Onboarding docs 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

• triage 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 Onboarding docs 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 (knowledge-onboardingdocs). 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.

### Onboarding docs Team - Firstweek Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Glean

Job:
Lists the documents new joiners actually open in week one.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Onboarding docs Team - Firstweek Bot
- Title: Lists the documents new joiners actually open in week one.
- Description: Lists the documents new joiners actually open in week one. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Onboarding docs Team - Wrong Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Checks those documents against current reality and names what is wrong.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Onboarding docs Team - Wrong Bot
- Title: Checks those documents against current reality and names what is wrong.
- Description: Checks those documents against current reality and names what is wrong. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Onboarding docs Team - Owner Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Google Drive

Job:
Names an owner for every first-week document, or flags that it has none.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Onboarding docs Team - Owner Bot
- Title: Names an owner for every first-week document, or flags that it has none.
- Description: Names an owner for every first-week document, or flags that it has none. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Onboarding docs Team - Draft Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Slack

Job:
Drafts the correction. Never publishes it.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Onboarding docs Team - Draft Bot
- Title: Drafts the correction.
- Description: Drafts the correction. Never publishes it. 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.

### Onboarding docs desk group chat
Members (4, two to six Bots): Onboarding docs Team - Firstweek Bot, Onboarding docs Team - Wrong Bot, Onboarding docs Team - Owner Bot, Onboarding docs Team - Draft 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.

### Accuracy pass
Owner Bot: Onboarding docs Team - Wrong Bot
Schedule: Every Monday at 10:00

Prompt to save (I will confirm the card):
Check first-week documents against current reality. Name every wrong statement.

### Owner check
Owner Bot: Onboarding docs Team - Owner Bot
Schedule: Every month on the 1st at 09:00

Prompt to save (I will confirm the card):
List first-week documents with no owner.

## 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.
- Glean: Draft. Use Glean read-only.
- Google Drive: Draft. Use Google Drive for drafts only. Write the page, never publish.
- Slack: Ask before send. Use Slack only after a human says yes in the chat. Say the post, wait for a yes.

## 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).

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


## 6. Also

Standing instructions for every Bot on this team:

- Never delete a page. Archive it and say so.
- Draft edits, never publish over someone.

## 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: Onboarding docs Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Notion, Glean, Google Drive. 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 ("Onboarding docs desk group chat", two to six Bots)
- I have created section "Onboarding docs 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.