Four Bots around a board meeting. Leads with bad news by design.
Board desk Team
Prepares board meetings from the real numbers, and tracks what was decided afterwards.
Bots
- Numbers Grok Bot
- Brief Grok Bot
- Actions Grok Bot
- Schedule Grok Bot
Board room group chat
- Numbers Grok BotPulls the operating numbers and shows the trend rather than a snapshot.
- Brief Grok BotDrafts the board brief, leading with what went badly.
- Actions Grok BotTracks decisions and actions from the last meeting and whether they happened.
- Schedule Grok BotHolds meeting dates and the deadline for circulating the brief.
Notion
Stripe
Google Calendar
Gmail
Numbers Grok BotGrok Bot
Pulls the operating numbers and shows the trend rather than a snapshot.
Stripe
Brief Grok BotGrok Bot
Drafts the board brief, leading with what went badly.
Notion
Actions Grok BotGrok Bot
Tracks decisions and actions from the last meeting and whether they happened.
Notion
Schedule Grok BotGrok Bot
Holds meeting dates and the deadline for circulating the brief.
Google Calendar
Gmail
Action check
Owner: Actions Grok BotEvery Monday at 09:00
List board actions from last meeting and their status. Name anything not started.
Brief deadline
Owner: Schedule Grok BotEvery weekday at 08:00
Name the next board date and whether the brief is on track to circulate on time.
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
grill-me by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Founder OS
Run Board desk 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 Board 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 (founder-board). 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.
### Board desk Team - Numbers Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Stripe
Job:
Pulls the operating numbers and shows the trend rather than a snapshot.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Board desk Team - Numbers Bot
- Title: Pulls the operating numbers and shows the trend rather than a snapshot.
- Description: Pulls the operating numbers and shows the trend rather than a snapshot. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Board desk Team - Brief Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Drafts the board brief, leading with what went badly.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Board desk Team - Brief Bot
- Title: Drafts the board brief, leading with what went badly.
- Description: Drafts the board brief, leading with what went badly. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Board desk Team - Actions Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Tracks decisions and actions from the last meeting and whether they happened.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Board desk Team - Actions Bot
- Title: Tracks decisions and actions from the last meeting and whether they happened.
- Description: Tracks decisions and actions from the last meeting and whether they happened. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Board desk Team - Schedule Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar, Gmail
Job:
Holds meeting dates and the deadline for circulating the brief.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Board desk Team - Schedule Bot
- Title: Holds meeting dates and the deadline for circulating the brief.
- Description: Holds meeting dates and the deadline for circulating the brief. 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.
### Board room group chat
Members (4, two to six Bots): Board desk Team - Numbers Bot, Board desk Team - Brief Bot, Board desk Team - Actions Bot, Board desk 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.
### Action check
Owner Bot: Board desk Team - Actions Bot
Schedule: Every Monday at 09:00
Prompt to save (I will confirm the card):
List board actions from last meeting and their status. Name anything not started.
### Brief deadline
Owner Bot: Board desk Team - Schedule Bot
Schedule: Every weekday at 08:00
Prompt to save (I will confirm the card):
Name the next board date and whether the brief is on track to circulate on time.
## 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.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- Stripe: Read. Use Stripe read-only. Never move funds.
- Calendar: Draft. Use Google Calendar for drafts only. Draft the event, do not send invites.
- 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).
### grill-me
https://skillselion.com/skills/mattpocock/skills/grill-me
Creator: mattpocock
Skill id: `skill:mattpocock/skills#grill-me`.
Scope: every Bot on this team (team scope).
## 6. Also
Standing instructions for every Bot on this team:
- Never send mail. Draft only.
- Never move funds.
## 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: Board desk Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Notion, Stripe, Calendar, 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 ("Board room group chat", two to six Bots)
- I have created section "Board 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.Teams that share these connectors
- Company TeamFeatured. Pinned first on the directory.
Six Bots run the company week. Product holds the list. Coding ships. Findability is SEO, AEO, and GEO. Marketing drafts. Trust reads security and legal. Money reads Stripe.
GitHub
Gmail
Google Calendar
Notion
Stripe
RampGoogle Search Console
Ahrefs
Exa
Firecrawl
- Fundraise desk Team
Runs a raise like a pipeline: who was met, what they asked, what was promised, and what is outstanding.
Gmail
Google Calendar
Notion
HubSpot
- Founder hiring Team
Handles hiring while it is still the founder's job, without letting candidates sit unanswered.
Gmail
Google Calendar
AshbyNotion

