Field events 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

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

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

### Field events Team - Guests Bot
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 Team - Guests 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.

### Field events Team - Budget Bot
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 Team - Budget 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.

### Field events Team - Run Bot
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 Team - Run 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.

### Field events Team - Thanks Bot
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 Team - Thanks 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.

## 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 Team - Guests Bot, Field events Team - Budget Bot, Field events Team - Run Bot, Field events Team - Thanks 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.

### Guest read
Owner Bot: Field events Team - Guests 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 Team - Budget 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.

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

- Luma: Draft. Use Luma for drafts only. Draft the event, do not send invites.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- Ramp: Read. Use Ramp read-only. Never move funds.
- Gmail: Draft. Use Gmail for drafts only. Draft the message, do not send.

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


## 6. Also

Standing instructions for every Bot on this team:

- Never email attendees without a human yes.
- Never change a booking or a contract.

## 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: Field events Team. Move the group chat and Bots into it.
- In Settings → Plugins, 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.
- Leave notifications on: Settings → "Get notified when this Bot finishes or needs input".

## Done when

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