• find-skills by vercel-labs

  … · Fetch at run · View on Skillselion

• handoff by mattpocock

  … · Fetch at run · View on Skillselion

• triage by mattpocock

  … · 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 Enterprise rollout 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, then Plugins.

From https://botteams.ai (onboarding-enterprise). Source: https://github.com/ellelion/botteams.

## 1. Create these Bots

Create each Bot below. Use the names exactly, including any prefix. After create, set Name, Title, and Description on the profile, then tell me to set the avatar.
A Bot is a single persistent, named agent. Conversation is the task; Title is the one-line job; Description holds durable rules and approvals.

### Enterprise rollout · Plan Grok Bot
(Named "Rollout · Plan" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Holds the rollout plan by department with named owners.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Enterprise rollout · Plan Grok Bot
- Title: Holds the rollout plan by department with named owners.
- Description: Holds the rollout plan by department with named owners. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Enterprise rollout · Champions Grok Bot
(Named "Rollout · Champions" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot

Job:
Tracks who is actually driving it inside the customer, and flags when they go quiet.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Enterprise rollout · Champions Grok Bot
- Title: Tracks who is actually driving it inside the customer, and flags when they go quiet.
- Description: Tracks who is actually driving it inside the customer, and flags when they go quiet. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Enterprise rollout · Sessions Grok Bot
(Named "Rollout · Sessions" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Schedules training per department and reports attendance.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Enterprise rollout · Sessions Grok Bot
- Title: Schedules training per department and reports attendance.
- Description: Schedules training per department and reports attendance. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

### Enterprise rollout · Adoption Grok Bot
(Named "Rollout · Adoption" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Microsoft Teams

Job:
Reports adoption by department, not company-wide, because averages hide the problem.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Enterprise rollout · Adoption Grok Bot
- Title: Reports adoption by department, not company-wide, because averages hide the problem.
- Description: Reports adoption by department, not company-wide, because averages hide the problem. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
Then tell me to open Edit Profile and set the avatar. You cannot stamp a custom image yourself unless I attach one.
If you create this Bot from an existing Bot, ask the new Bot to set those profile fields after create.

## 2. Create this group chat

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

### Rollout room group chat
Members (4, two to six Bots): Enterprise rollout · Plan Grok Bot, Enterprise rollout · Champions Grok Bot, Enterprise rollout · Sessions Grok Bot, Enterprise rollout · Adoption Grok Bot

## 3. Sidebar section

You cannot create sidebar sections. When the Bots and group chat exist, tell me to Move to, then New section.
I will name that section exactly: Onboarding.
Ask me to move the group chat and Bots into it.

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

### Champion check
Owner Bot: Enterprise rollout · Champions Grok Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Name customer champions who have gone quiet for more than two weeks.

### Adoption by team
Owner Bot: Enterprise rollout · Adoption Grok Bot
Schedule: Every Monday at 09:30

Prompt to save (I will confirm the card):
Report adoption per department. Name the lowest three and how long they have been low.

## 5. 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, then 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.

- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Microsoft Teams: Ask before send. Use Microsoft Teams only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Calendar, Notion. That switch is account-wide and it is the only one that actually stops a write.

## 6. Skills

Skills live under Settings → Plugins → Yours, and they are per Bot. Enable the ones listed here for the named Bots. Reference a skill with /.
You cannot flip the human Notifications toggle. Tell me to leave Settings → “Get notified when this Bot finishes or needs input” on.
Do not pin or hide a Bot unless I say so. Hide does not pause routines.
Sidebar sections are human-only: tell me to Move to → New section. A group chat holds two to six Bots. An account holds 50 Bots and group chats combined. One Bot can own 50 routines. Confirm cards stay on me.
If a workflow should be demonstrated later, mention Teach a task after the first success (browser workflows).

Connect the Skillselion connector first if any skill below is Fetch at run (Settings → Plugins). Do not start OAuth from this prompt.

### find-skills
https://skillselion.com/skills/vercel-labs/skills/find-skills
Creator: vercel-labs
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:vercel-labs/skills#find-skills`. Connect Skillselion in Settings → Plugins first.

### handoff
https://skillselion.com/skills/mattpocock/skills/handoff
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#handoff`. Connect Skillselion in Settings → Plugins first.

### triage
https://skillselion.com/skills/mattpocock/skills/triage
Creator: mattpocock
Scope: every Bot on this team (team scope).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#triage`. Connect Skillselion in Settings → Plugins first.


## 7. Also

Standing instructions for every Bot on this team:

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

## Done when

- Named Bots exist
- Named group chat exists ("Rollout room group chat", two to six Bots)
- I have created section "Onboarding"
- 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.