Demo desk 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 Demo desk 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 (sales-demos). 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.

### Demo desk Team - Prep Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot

Job:
Assembles what is known about the account before the call.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk Team - Prep Bot
- Title: Assembles what is known about the account before the call.
- Description: Assembles what is known about the account before the call. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Demo desk Team - Plan Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Drafts the demo plan around their stated problem, not the standard tour.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk Team - Plan Bot
- Title: Drafts the demo plan around their stated problem, not the standard tour.
- Description: Drafts the demo plan around their stated problem, not the standard tour. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Demo desk Team - Promises Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gong

Job:
Pulls commitments made during the call from the recording.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk Team - Promises Bot
- Title: Pulls commitments made during the call from the recording.
- Description: Pulls commitments made during the call from the recording. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Demo desk Team - Follow Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Drafts the follow-up covering exactly what was promised. Never sends.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Demo desk Team - Follow Bot
- Title: Drafts the follow-up covering exactly what was promised.
- Description: Drafts the follow-up covering exactly what was promised. Never sends. 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.

### Demo desk group chat
Members (4, two to six Bots): Demo desk Team - Prep Bot, Demo desk Team - Plan Bot, Demo desk Team - Promises Bot, Demo desk Team - Follow 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.

### Prep brief
Owner Bot: Demo desk Team - Prep Bot
Schedule: Every weekday at 08:00

Prompt to save (I will confirm the card):
For today's demos, assemble what is known and what to ask.

### Promise pull
Owner Bot: Demo desk Team - Promises Bot
Schedule: Every weekday at 17:00

Prompt to save (I will confirm the card):
From today's calls, list every commitment made to a prospect and who owns it.

## 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.
- Gong: Draft. Use Gong read-only.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.

## 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 a prospect. Draft only.
- Never discount without a human yes.

## 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: Demo desk Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Calendar, Gong, 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 ("Demo desk group chat", two to six Bots)
- I have created section "Demo desk 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.