Enterprise rollout 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 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 → Plugins.

From https://botteams.io (onboarding-enterprise). 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.

### Enterprise rollout Team - Plan Bot
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 Team - Plan 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.

### Enterprise rollout Team - Champions Bot
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 Team - Champions 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.

### Enterprise rollout Team - Sessions Bot
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 Team - Sessions 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.

### Enterprise rollout Team - Adoption Bot
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 Team - Adoption 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.

## 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 Team - Plan Bot, Enterprise rollout Team - Champions Bot, Enterprise rollout Team - Sessions Bot, Enterprise rollout Team - Adoption 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.

### Champion check
Owner Bot: Enterprise rollout Team - Champions 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 Team - Adoption 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.

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

- HubSpot: Ask before send. Use HubSpot only after a human says yes in the chat. Say the post, wait for a yes.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Microsoft Teams: Ask before send. Use Microsoft Teams 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 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: Enterprise rollout Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Calendar, Notion. 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 ("Rollout room group chat", two to six Bots)
- I have created section "Enterprise rollout 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.