Event sponsorship 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 Event sponsorship 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-sponsorship). 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.

### Event sponsorship Team - Terms Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Records what the sponsorship actually included, in a checkable list.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Event sponsorship Team - Terms Bot
- Title: Records what the sponsorship actually included, in a checkable list.
- Description: Records what the sponsorship actually included, in a checkable list. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Event sponsorship Team - Delivered Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Checks each promised item against what appeared.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Event sponsorship Team - Delivered Bot
- Title: Checks each promised item against what appeared.
- Description: Checks each promised item against what appeared. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Event sponsorship Team - Cost Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Ramp

Job:
Tracks total cost including the parts nobody budgets for.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Event sponsorship Team - Cost Bot
- Title: Tracks total cost including the parts nobody budgets for.
- Description: Tracks total cost including the parts nobody budgets for. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Event sponsorship Team - Leads Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot, Gmail

Job:
Counts the conversations that turned into pipeline, honestly.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Event sponsorship Team - Leads Bot
- Title: Counts the conversations that turned into pipeline, honestly.
- Description: Counts the conversations that turned into pipeline, honestly. 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.

### Sponsorship desk group chat
Members (4, two to six Bots): Event sponsorship Team - Terms Bot, Event sponsorship Team - Delivered Bot, Event sponsorship Team - Cost Bot, Event sponsorship Team - Leads 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.

### Delivery check
Owner Bot: Event sponsorship Team - Delivered Bot
Schedule: Every weekday at 16:00

Prompt to save (I will confirm the card):
For live sponsorships, list promised items not yet delivered.

### Return read
Owner Bot: Event sponsorship Team - Leads Bot
Schedule: Every month on the 1st at 10:00

Prompt to save (I will confirm the card):
Report pipeline from each event against total cost. Do not round in our favour.

## 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.
- Ramp: Read. Use Ramp read-only. Never move funds.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- 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: Event sponsorship Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Ramp, Notion, 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 ("Sponsorship desk group chat", two to six Bots)
- I have created section "Event sponsorship 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.