Four Bots on the calendar. Reports cost, cancels nothing.
Meeting hygiene Team
Makes the real cost of the calendar visible, and kills the meetings nobody would defend.
Bots
- Cost Grok Bot
- Agenda Grok Bot
- Attendance Grok Bot
- Recap Grok Bot
Meeting desk group chat
- Cost Grok BotReports hours spent in recurring meetings per team.
- Agenda Grok BotNames recurring meetings with no agenda and no notes.
- Attendance Grok BotFinds meetings where most invitees never speak.
- Recap Grok BotDrafts the case for cancelling specific meetings.
Google Calendar
Microsoft Teams
Notion
Gmail
Cost Grok BotGrok Bot
Reports hours spent in recurring meetings per team.
Google Calendar
Agenda Grok BotGrok Bot
Names recurring meetings with no agenda and no notes.
Notion
Attendance Grok BotGrok Bot
Finds meetings where most invitees never speak.
Microsoft Teams
Recap Grok BotGrok Bot
Drafts the case for cancelling specific meetings.
Gmail
Cost read
Owner: Cost Grok BotEvery Monday at 09:00
Report hours in recurring meetings per team. Name the five most expensive.
Agenda check
Owner: Agenda Grok BotEvery Friday at 14:00
List recurring meetings held this week with no agenda and no notes.
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
triage by mattpocockLooking up counts on Skillselion. · Fetch at run · View on Skillselion
Sidebar section
Workplace
Run Meeting hygiene 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 Meeting hygiene 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 (workplace-meetings). 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.
### Meeting hygiene Team - Cost Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Calendar
Job:
Reports hours spent in recurring meetings per team.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Meeting hygiene Team - Cost Bot
- Title: Reports hours spent in recurring meetings per team.
- Description: Reports hours spent in recurring meetings per team. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Meeting hygiene Team - Agenda Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Names recurring meetings with no agenda and no notes.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Meeting hygiene Team - Agenda Bot
- Title: Names recurring meetings with no agenda and no notes.
- Description: Names recurring meetings with no agenda and no notes. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Meeting hygiene Team - Attendance Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Microsoft Teams
Job:
Finds meetings where most invitees never speak.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Meeting hygiene Team - Attendance Bot
- Title: Finds meetings where most invitees never speak.
- Description: Finds meetings where most invitees never speak. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Meeting hygiene Team - Recap Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts the case for cancelling specific meetings.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Meeting hygiene Team - Recap Bot
- Title: Drafts the case for cancelling specific meetings.
- Description: Drafts the case for cancelling specific meetings. 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.
### Meeting desk group chat
Members (4, two to six Bots): Meeting hygiene Team - Cost Bot, Meeting hygiene Team - Agenda Bot, Meeting hygiene Team - Attendance Bot, Meeting hygiene Team - Recap 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.
### Cost read
Owner Bot: Meeting hygiene Team - Cost Bot
Schedule: Every Monday at 09:00
Prompt to save (I will confirm the card):
Report hours in recurring meetings per team. Name the five most expensive.
### Agenda check
Owner Bot: Meeting hygiene Team - Agenda Bot
Schedule: Every Friday at 14:00
Prompt to save (I will confirm the card):
List recurring meetings held this week with no agenda and no notes.
## 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.
- Microsoft Teams: Ask before send. Use Microsoft Teams only after a human says yes in the chat. Say the post, wait for a yes.
- Notion: Draft. Use Notion for drafts only. Write the page, never publish.
- 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).
### triage
https://skillselion.com/skills/mattpocock/skills/triage
Creator: mattpocock
Skill id: `skill:mattpocock/skills#triage`.
Scope: every Bot on this team (team scope).
## 6. Also
Standing instructions for every Bot on this team:
- Never mail the whole company without a yes.
- Never book or cancel anything for anyone.
## 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: Meeting hygiene Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for Calendar, Notion, 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 ("Meeting desk group chat", two to six Bots)
- I have created section "Meeting hygiene 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
- IT requests Team
Runs the internal IT queue so requests do not sit unanswered and access is granted deliberately.
Microsoft Teams
1Password
Notion
Gmail
- Policy desk Team
Keeps internal policies findable and current, and tracks who has actually read them.
Notion
SharePoint
Gmail
Glean
- Software spend Team
Finds the subscriptions nobody uses and the ones nobody remembers approving.
RampXero
Notion
Microsoft Teams

