• 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 Field events 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 (events-field). 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.

### Field events · Guests Grok Bot
(Named "Field · Guests" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Luma

Job:
Tracks invited, confirmed, and likely-to-show, and says which is which.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Field events · Guests Grok Bot
- Title: Tracks invited, confirmed, and likely-to-show, and says which is which.
- Description: Tracks invited, confirmed, and likely-to-show, and says which is which. 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.

### Field events · Budget Grok Bot
(Named "Field · Budget" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ramp

Job:
Watches spend against budget in Ramp and names overruns early.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Field events · Budget Grok Bot
- Title: Watches spend against budget in Ramp and names overruns early.
- Description: Watches spend against budget in Ramp and names overruns early. 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.

### Field events · Run Grok Bot
(Named "Field · Run" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Holds the timings and the supplier list for the day.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Field events · Run Grok Bot
- Title: Holds the timings and the supplier list for the day.
- Description: Holds the timings and the supplier list for the day. 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.

### Field events · Thanks Grok Bot
(Named "Field · Thanks" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail

Job:
Drafts the thank-you naming what each guest actually talked about.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Field events · Thanks Grok Bot
- Title: Drafts the thank-you naming what each guest actually talked about.
- Description: Drafts the thank-you naming what each guest actually talked about. 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.

### Field desk group chat
Members (4, two to six Bots): Field events · Guests Grok Bot, Field events · Budget Grok Bot, Field events · Run Grok Bot, Field events · Thanks 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: Events.
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.

### Guest read
Owner Bot: Field events · Guests Grok Bot
Schedule: Every weekday at 10:00

Prompt to save (I will confirm the card):
Report invited, confirmed, and likely-to-show for upcoming events. Flag under-target.

### Budget watch
Owner Bot: Field events · Budget Grok Bot
Schedule: Every weekday at 11:00

Prompt to save (I will confirm the card):
Report spend against budget per event. Name anything trending over.

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

- Luma: Draft. Use Luma for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Calendar: Draft. Use Calendar for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Ramp: Read. Use Ramp read-only. Read and summarise it. Do not create, edit, send, move, or delete anything in Ramp.
- Gmail: Draft. Use Gmail 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 Luma, Calendar, Ramp, Gmail. 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 email attendees without a human yes.
- Never change a booking or a contract.

## Done when

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