Four Bots preparing reviews. Leads with the bad news on purpose.
Quarterly reviews Team
Prepares the quarterly business review from real usage and real outcomes, not a slide template.
Bots
- Usage Grok Bot
- Promises Grok Bot
- Deck Grok Bot
- Schedule Grok Bot
Review desk group chat
- Usage Grok BotPulls the quarter's real usage per account and shows the trend, not just the total.
- Promises Grok BotLists what was promised at the last review and whether it happened.
- Deck Grok BotDrafts the review in Notion, leading with anything that went badly.
- Schedule Grok BotBooks the reviews and names which accounts are overdue one.
HubSpot
Mixpanel
Notion
Google Calendar
Usage Grok BotGrok Bot
Pulls the quarter's real usage per account and shows the trend, not just the total.
Mixpanel
Promises Grok BotGrok Bot
Lists what was promised at the last review and whether it happened.
HubSpot
Deck Grok BotGrok Bot
Drafts the review in Notion, leading with anything that went badly.
Notion
Schedule Grok BotGrok Bot
Books the reviews and names which accounts are overdue one.
Google Calendar
Overdue reviews
Owner: Schedule Grok BotEvery Monday at 09:00
List accounts overdue a quarterly review, longest first.
Promise check
Owner: Promises Grok BotEvery quarter on the 1st at 10:00
For each account, list what was promised last review and whether it happened.
find-skills by vercel-labsLooking up counts on Skillselion. · Fetch at run · View on Skillselion
handoff by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
tdd by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
improve-codebase-architecture by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
setup-matt-pocock-skills by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Customer success
Run Quarterly reviews yourself
Free to copy, adapt, and edit. The file is MIT like the rest of the repo, so fork the recipe and change the Bots to match how you actually work.
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 Quarterly reviews 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 (success-qbr). 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.
### Quarterly reviews Team - Usage Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Mixpanel
Job:
Pulls the quarter's real usage per account and shows the trend, not just the total.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Quarterly reviews Team - Usage Bot
- Title: Pulls the quarter's real usage per account and shows the trend, not just the total.
- Description: Pulls the quarter's real usage per account and shows the trend, not just the total. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Quarterly reviews Team - Promises Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): HubSpot
Job:
Lists what was promised at the last review and whether it happened.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Quarterly reviews Team - Promises Bot
- Title: Lists what was promised at the last review and whether it happened.
- Description: Lists what was promised at the last review and whether it happened. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Quarterly reviews Team - Deck Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Drafts the review in Notion, leading with anything that went badly.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Quarterly reviews Team - Deck Bot
- Title: Drafts the review in Notion, leading with anything that went badly.
- Description: Drafts the review in Notion, leading with anything that went badly. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Quarterly reviews Team - Schedule Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar
Job:
Books the reviews and names which accounts are overdue one.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Quarterly reviews Team - Schedule Bot
- Title: Books the reviews and names which accounts are overdue one.
- Description: Books the reviews and names which accounts are overdue one. 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.
### Review desk group chat
Members (4, two to six Bots): Quarterly reviews Team - Usage Bot, Quarterly reviews Team - Promises Bot, Quarterly reviews Team - Deck Bot, Quarterly reviews Team - Schedule 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.
### Overdue reviews
Owner Bot: Quarterly reviews Team - Schedule Bot
Schedule: Every Monday at 09:00
Prompt to save (I will confirm the card):
List accounts overdue a quarterly review, longest first.
### Promise check
Owner Bot: Quarterly reviews Team - Promises Bot
Schedule: Every quarter on the 1st at 10:00
Prompt to save (I will confirm the card):
For each account, list what was promised last review and whether it happened.
## 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.
- Mixpanel: Draft. Use Mixpanel read-only.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
## 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).
### tdd
https://skillselion.com/skills/mattpocock/skills/tdd
Creator: mattpocock
Skill id: `skill:mattpocock/skills#tdd`.
Scope: only Quarterly reviews Team - Promises Bot.
### improve-codebase-architecture
https://skillselion.com/skills/mattpocock/skills/improve-codebase-architecture
Creator: mattpocock
Skill id: `skill:mattpocock/skills#improve-codebase-architecture`.
Scope: only Quarterly reviews Team - Promises Bot.
### setup-matt-pocock-skills
https://skillselion.com/skills/mattpocock/skills/setup-matt-pocock-skills
Creator: mattpocock
Skill id: `skill:mattpocock/skills#setup-matt-pocock-skills`.
Scope: only Quarterly reviews Team - Promises Bot.
## 6. Also
Standing instructions for every Bot on this team:
- Never send to a customer without a human yes.
- Never promise a date engineering has not agreed.
## 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: Quarterly reviews Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Mixpanel, Notion, Calendar. 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 ("Review desk group chat", two to six Bots)
- I have created section "Quarterly reviews 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.Teams that share these connectors
- Customer success Team
Watches account health, renewals, and quarterly reviews, and names the accounts that need a human conversation this week.
Gmail
Google Calendar
Stripe
Zendesk
HubSpot
Gong
- Account health Team
Turns scattered usage and support signals into a plain answer about which accounts are actually in trouble.
HubSpot
Zendesk
Mixpanel
Gmail
- Account onboarding Team
Runs the first ninety days of a new account so the handover from sales does not quietly become nobody's job.
Gmail
Google Calendar
HubSpot
Notion

