Studio capacity 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 Studio capacity 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 (agency-capacity). 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.

### Studio capacity Team - Booked Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar

Job:
Adds up committed delivery time per person from Calendar for the next four weeks.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Studio capacity Team - Booked Bot
- Title: Adds up committed delivery time per person from Calendar for the next four weeks.
- Description: Adds up committed delivery time per person from Calendar for the next four weeks. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Studio capacity Team - Pipeline Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion

Job:
Reads the Notion pipeline and estimates the hours attached to work likely to land.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Studio capacity Team - Pipeline Bot
- Title: Reads the Notion pipeline and estimates the hours attached to work likely to land.
- Description: Reads the Notion pipeline and estimates the hours attached to work likely to land. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Studio capacity Team - Work Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Linear

Job:
Tracks live project tasks in Linear and flags the ones with no owner or no date.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Studio capacity Team - Work Bot
- Title: Tracks live project tasks in Linear and flags the ones with no owner or no date.
- Description: Tracks live project tasks in Linear and flags the ones with no owner or no date. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.

### Studio capacity Team - Answer Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.

Job:
Says yes, no, or yes-if for the next project, with the constraint named. Never commits the studio to anything.

After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Studio capacity Team - Answer Bot
- Title: Says yes, no, or yes-if for the next project, with the constraint named.
- Description: Says yes, no, or yes-if for the next project, with the constraint named. Never commits the studio to anything. 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.

### Capacity room group chat
Members (4, two to six Bots): Studio capacity Team - Booked Bot, Studio capacity Team - Pipeline Bot, Studio capacity Team - Work Bot, Studio capacity Team - Answer 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.

### Capacity read
Owner Bot: Studio capacity Team - Answer Bot
Schedule: Every Monday at 09:00

Prompt to save (I will confirm the card):
Give the four-week capacity read per person: booked, likely, free. Name the first week that is over.

### Unowned work
Owner Bot: Studio capacity Team - Work Bot
Schedule: Every weekday at 11:00

Prompt to save (I will confirm the card):
List live Linear tasks with no owner or no due date. Never assign anything.

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

- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Linear: Draft. Use Linear 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 send client mail. Draft only.
- Never change a signed scope without asking.

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