• find-skills by vercel-labs

  … · Fetch at run · View on Skillselion

• handoff 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 Revenue forecast 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 (revenue-forecast). 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.

### Revenue forecast · Commit Grok Bot
(Named "Forecast · Commit" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Salesforce

Job:
Separates committed pipeline from optimistic pipeline.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Revenue forecast · Commit Grok Bot
- Title: Separates committed pipeline from optimistic pipeline.
- Description: Separates committed pipeline from optimistic pipeline. 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.

### Revenue forecast · History Grok Bot
(Named "Forecast · History" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Reports how accurate the last three forecasts were.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Revenue forecast · History Grok Bot
- Title: Reports how accurate the last three forecasts were.
- Description: Reports how accurate the last three forecasts were. 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.

### Revenue forecast · Recurring Grok Bot
(Named "Forecast · Recurring" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Stripe

Job:
Reads Stripe for the recurring base beneath the forecast.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Revenue forecast · Recurring Grok Bot
- Title: Reads Stripe for the recurring base beneath the forecast.
- Description: Reads Stripe for the recurring base beneath the forecast. 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.

### Revenue forecast · Risk Grok Bot
(Named "Forecast · Risk" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot

Job:
Names the deals the forecast depends on most.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Revenue forecast · Risk Grok Bot
- Title: Names the deals the forecast depends on most.
- Description: Names the deals the forecast depends on most. 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.

### Forecast desk group chat
Members (4, two to six Bots): Revenue forecast · Commit Grok Bot, Revenue forecast · History Grok Bot, Revenue forecast · Recurring Grok Bot, Revenue forecast · Risk 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: Revenue.
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.

### Weekly forecast
Owner Bot: Revenue forecast · Commit Grok Bot
Schedule: Every Monday at 08:00

Prompt to save (I will confirm the card):
Report committed versus optimistic pipeline. Name the three deals the number depends on.

### Accuracy check
Owner Bot: Revenue forecast · History Grok Bot
Schedule: Every month on the 1st at 09:00

Prompt to save (I will confirm the card):
Report how wrong the last three forecasts were, and in which direction.

## 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.
- Salesforce: Ask before send. Use Salesforce only after a human says yes in the chat. State exactly what you are about to do, wait for the reply, then act.
- Stripe: Read. Use Stripe read-only. Read and summarise it. Do not create, edit, send, move, or delete anything in Stripe.
- Notion: Draft. Use Notion for drafts only. Leave every draft unsent and every change unsaved so a human can review it.

Human: the lines above are instructions, not permissions. In Grok Bot open Settings, then Plugins, and disable the write tools for Stripe, 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.


## 7. Also

Standing instructions for every Bot on this team:

- Never move money or issue a credit.
- Never mail a customer about billing without a yes.

## Done when

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