Metric definitions Team

• find-skills by vercel-labs

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

• handoff by mattpocock

  Looking up counts on Skillselion. · Fetch at run · View on Skillselion

Paste the prompt into Grok Bot. This is not one-click OAuth and nothing is installed on this site.

# Grok Bot Teams installer

Set up a team for me called Metric definitions Team. Create the named Bots, then the group chat, then save the routines.
Ask me only for things you cannot see. Do not start OAuth. If a connector is missing, tell me to connect it in Settings → Plugins.

From https://botteams.io (data-metrics). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly. After create, set Name, Title, and Description on the profile.
A Bot is persistent and named. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Metric definitions Team - Registry Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Holds the definition of every headline metric and where it is computed.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Metric definitions Team - Registry Bot
- Title: Holds the definition of every headline metric and where it is computed.
- Description: Holds the definition of every headline metric and where it is computed. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Metric definitions Team - Drift Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): dbt Labs

Job:
Finds places where the same metric is computed differently and names both.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Metric definitions Team - Drift Bot
- Title: Finds places where the same metric is computed differently and names both.
- Description: Finds places where the same metric is computed differently and names both. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Metric definitions Team - Check Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Cloud BigQuery

Job:
Recomputes headline metrics from source and compares to what dashboards show.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Metric definitions Team - Check Bot
- Title: Recomputes headline metrics from source and compares to what dashboards show.
- Description: Recomputes headline metrics from source and compares to what dashboards show. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Metric definitions Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Reports which definitions changed and who should know.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Metric definitions Team - Recap Bot
- Title: Reports which definitions changed and who should know.
- Description: Reports which definitions changed and who should know. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

## 2. Create this group chat

Open a group chat with two to six of the Bots above. Do not add more than six.

### Definitions desk group chat
Members (4, two to six Bots): Metric definitions Team - Registry Bot, Metric definitions Team - Drift Bot, Metric definitions Team - Check Bot, Metric definitions Team - Recap Bot

## 3. Routines (confirm card required)

Ping each owner Bot with the routine they own so they can save it.
A routine is owned by one Bot, and one Bot can own up to 50 of them. A confirm card will appear. I will confirm each one.
Do not assume a routine is saved until I confirm.

### Drift scan
Owner Bot: Metric definitions Team - Drift Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Find metrics computed more than one way. Show both definitions side by side.

### Recompute
Owner Bot: Metric definitions Team - Check Bot
Schedule: Every weekday at 08:00

Prompt to save (I will confirm the card):
Recompute headline metrics from source and report any that disagree with the dashboard.

## 4. Connectors and how far they go

Connectors are account-wide. They must already be connected.
If any are missing, tell me to connect them in Settings → Plugins first.
Do not walk an OAuth flow from this prompt.
Every Bot on this account can reach every connected tool. The lists above are which Bot is expected to use which, not a second OAuth and not a boundary.

- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- dbt Labs: Draft. Use dbt Labs read-only.
- Google Cloud BigQuery: Draft. Use Google Cloud BigQuery read-only.

## 5. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Reference a skill with /.
If a skill is already installed on the account (Settings → Plugins → Yours), use it. Enable it for this Bot if / does not show it.
If it is not installed, fetch or load it through the Skillselion connector using the skill id. Do not install a second copy.
Connect the Skillselion connector only when a fetch is needed. Do not start OAuth from this prompt.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Skill id: `skill:vercel-labs/skills#find-skills`.
Scope: every Bot on this team (team scope).

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Skill id: `skill:mattpocock/skills#handoff`.
Scope: every Bot on this team (team scope).


## 6. Also

Standing instructions for every Bot on this team:

- Read only. Never write back to a warehouse table.
- Never present a number without the query behind it.

## Human steps

These are yours. The Bot cannot do them.

- Set each Bot avatar (Bot actions → Edit Profile). Attach an image if you want a custom one.
- Create a sidebar section named exactly: Metric definitions Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Notion, dbt Labs, Google Cloud BigQuery. That switch is account-wide and it is the only one that actually stops a write.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".

## Done when

- Named Bots exist
- Named group chat exists ("Definitions desk group chat", two to six Bots)
- I have created section "Metric definitions Team"
- Each routine has a confirmed save (or I declined)
- Connectors listed above are already connected

Uninstall: delete the Bots and group chats in the Grok Bot sidebar.
There is no remote uninstall from this catalog.