Technical onboarding 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 Technical onboarding 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 (onboarding-technical). 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.

### Technical onboarding Team - Progress Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Mixpanel

Job:
Tracks each customer against the integration steps and names where they stalled.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical onboarding Team - Progress Bot
- Title: Tracks each customer against the integration steps and names where they stalled.
- Description: Tracks each customer against the integration steps and names where they stalled. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Technical onboarding Team - Blockers Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Intercom

Job:
Reads support threads for the blockers customers hit repeatedly.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical onboarding Team - Blockers Bot
- Title: Reads support threads for the blockers customers hit repeatedly.
- Description: Reads support threads for the blockers customers hit repeatedly. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Technical onboarding Team - Docs Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Drafts the doc fix for a blocker that keeps recurring.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical onboarding Team - Docs Bot
- Title: Drafts the doc fix for a blocker that keeps recurring.
- Description: Drafts the doc fix for a blocker that keeps recurring. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Technical onboarding Team - Bugs Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear

Job:
Files the Linear issue when the blocker is a product problem.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Technical onboarding Team - Bugs Bot
- Title: Files the Linear issue when the blocker is a product problem.
- Description: Files the Linear issue when the blocker is a product problem. 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.

### Technical onboarding desk group chat
Members (4, two to six Bots): Technical onboarding Team - Progress Bot, Technical onboarding Team - Blockers Bot, Technical onboarding Team - Docs Bot, Technical onboarding Team - Bugs 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.

### Stall report
Owner Bot: Technical onboarding Team - Progress Bot
Schedule: Every weekday at 09:00

Prompt to save (I will confirm the card):
List customers stalled at the same integration step for more than three days.

### Blocker pattern
Owner Bot: Technical onboarding Team - Blockers Bot
Schedule: Every Friday at 14:00

Prompt to save (I will confirm the card):
Name blockers hit by three or more customers this week.

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

- Intercom: Ask before send. Use Intercom only after a human says yes in the chat. Say the post, wait for a yes.
- Linear: Draft. Use Linear for drafts only. Write the page, never publish.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Mixpanel: Draft. Use Mixpanel 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).

### triage
https://skillselion.com/skills/mattpocock/skills/triage
Creator: mattpocock
Skill id: `skill:mattpocock/skills#triage`.
Scope: only Technical onboarding Team - Blockers Bot.


## 6. Also

Standing instructions for every Bot on this team:

- Never mail a new starter without a human yes.
- Never grant access to anything.

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