Four Bots ahead of the spike. Read-only against production.
Capacity planning team
Answers whether the system survives the next spike, before the spike rather than during it.
Capacity planning team
Answers whether the system survives the next spike, before the spike rather than during it.
Bots
- Trend Grok Bot
- Limits Grok Bot
- Edge Grok Bot
- Plan Grok Bot
Capacity desk group chat
- Trend Grok Bot
- Limits Grok Bot
- Edge Grok Bot
- Plan Grok Bot
Datadog
Cloudflare
Supabase
Notion
Job
Trend Grok BotGrok Bot
Projects load growth from the trailing quarter, not from last week.
Datadog
Limits Grok BotGrok Bot
Records the known ceiling for each component and how close it is.
Supabase
Edge Grok BotGrok Bot
Reports cache hit rates and what a miss actually costs.
Cloudflare
Plan Grok BotGrok Bot
Writes the capacity note naming the first thing that breaks.
Notion
Routines2
Trend read
Project load growth from the trailing quarter. Name the component that hits a limit first.
Limit check
Report each component against its known ceiling. Never change a limit.
Skills3
find-skills by vercel-labs… · Fetch at run · View on Skillselion
handoff by mattpocock… · Fetch at run · View on Skillselion
grill-me by mattpocock… · Fetch at run · View on Skillselion
Notes
Sidebar section
Infrastructure
Prompt Installer for Grok Bot
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 Capacity planning 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 (infra-capacity). 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.
### Capacity planning · Trend Grok Bot
(Named "Capacity · Trend" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Datadog
Job:
Projects load growth from the trailing quarter, not from last week.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Capacity planning · Trend Grok Bot
- Title: Projects load growth from the trailing quarter, not from last week.
- Description: Projects load growth from the trailing quarter, not from last week. 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.
### Capacity planning · Limits Grok Bot
(Named "Capacity · Limits" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Supabase
Job:
Records the known ceiling for each component and how close it is.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Capacity planning · Limits Grok Bot
- Title: Records the known ceiling for each component and how close it is.
- Description: Records the known ceiling for each component and how close it is. 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.
### Capacity planning · Edge Grok Bot
(Named "Capacity · Edge" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Cloudflare
Job:
Reports cache hit rates and what a miss actually costs.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Capacity planning · Edge Grok Bot
- Title: Reports cache hit rates and what a miss actually costs.
- Description: Reports cache hit rates and what a miss actually costs. 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.
### Capacity planning · Plan Grok Bot
(Named "Capacity · Plan" in the published recipe.)
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Writes the capacity note naming the first thing that breaks.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Capacity planning · Plan Grok Bot
- Title: Writes the capacity note naming the first thing that breaks.
- Description: Writes the capacity note naming the first thing that breaks. 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.
### Capacity desk group chat
Members (4, two to six Bots): Capacity planning · Trend Grok Bot, Capacity planning · Limits Grok Bot, Capacity planning · Edge Grok Bot, Capacity planning · Plan 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: Infrastructure.
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.
### Trend read
Owner Bot: Capacity planning · Trend Grok Bot
Schedule: Every Monday at 09:00
Prompt to save (I will confirm the card):
Project load growth from the trailing quarter. Name the component that hits a limit first.
### Limit check
Owner Bot: Capacity planning · Limits Grok Bot
Schedule: Every weekday at 08:00
Prompt to save (I will confirm the card):
Report each component against its known ceiling. Never change a limit.
## 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.
- Datadog: Draft. Use Datadog for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Cloudflare: Draft. Use Cloudflare for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Supabase: Draft. Use Supabase for drafts only. Leave every draft unsent and every change unsaved so a human can review it.
- Notion: Draft. Use Notion 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 Datadog, Cloudflare, Supabase, Notion. 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.
### grill-me
https://skillselion.com/skills/mattpocock/skills/grill-me
Creator: mattpocock
Scope: only Capacity · Plan (enable under Plugins → Yours for that Bot only).
Do not install. When this job comes up, use the Skillselion connector to search/load `skill:mattpocock/skills#grill-me`. Connect Skillselion in Settings → Plugins first.
## 7. Also
Standing instructions for every Bot on this team:
- Never apply a change. Draft the plan.
- Never touch production without a human yes.
## Done when
- Named Bots exist
- Named group chat exists ("Capacity desk group chat", two to six Bots)
- I have created section "Infrastructure"
- 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.Teams that share these connectors
- Backup and recovery
Checks that backups exist and could actually be restored, which is not the same question.
Supabase
AWS Core
Notion
PagerDuty
- Cloud cost
Turns a cloud bill into named decisions, so spend growth has an owner rather than a shrug.
AWS Core
Datadog
VantageNotion
- Security posture
Watches the boring security surface that gets ignored until it does not: keys, permissions, and exposed endpoints.
Cloudflare
GitHub
1Password
Snyk



