Four Bots noticing the people who help. Drafts thanks, sends none.
Advocate program Team
Finds the people already helping in public, keeps track of what they did, and makes sure they get thanked by a human.
Bots
- Spot Grok Bot
- Record Grok Bot
- Thanks Grok Bot
- Recap Grok Bot
Advocate room group chat
- Spot Grok BotNotices people repeatedly answering others in public and lists them with what they did.
- Record Grok BotKeeps the advocate record in Notion current: contributions, dates, and what they were sent.
- Thanks Grok BotDrafts a specific thank-you naming the actual thing they did.
- Recap Grok BotReports who helped most this month and who has gone quiet.
Discord
X Ads
Notion
Gmail
Spot Grok BotGrok Bot
Notices people repeatedly answering others in public and lists them with what they did.
Discord
X Ads
Record Grok BotGrok Bot
Keeps the advocate record in Notion current: contributions, dates, and what they were sent.
Notion
Thanks Grok BotGrok Bot
Drafts a specific thank-you naming the actual thing they did. Never sends a generic one and never sends at all.
Gmail
Recap Grok BotGrok Bot
Reports who helped most this month and who has gone quiet.
Advocate scan
Owner: Spot Grok BotEvery weekday at 16:00
List people who answered someone else in public today and what they answered.
Monthly thanks
Owner: Thanks Grok BotEvery month on the 1st at 10:00
Draft a specific thank-you for each advocate, naming what they actually did. Never send.
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
Sidebar section
Community
Run Advocate program 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 Advocate program 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 (community-advocates). 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.
### Advocate program Team - Spot Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Discord, X
Job:
Notices people repeatedly answering others in public and lists them with what they did.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Advocate program Team - Spot Bot
- Title: Notices people repeatedly answering others in public and lists them with what they did.
- Description: Notices people repeatedly answering others in public and lists them with what they did. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Advocate program Team - Record Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Notion
Job:
Keeps the advocate record in Notion current: contributions, dates, and what they were sent.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Advocate program Team - Record Bot
- Title: Keeps the advocate record in Notion current: contributions, dates, and what they were sen…
- Description: Keeps the advocate record in Notion current: contributions, dates, and what they were sent. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Advocate program Team - Thanks Bot
Create this Bot. Use the name exactly.
Uses connectors (already on the account): Gmail
Job:
Drafts a specific thank-you naming the actual thing they did. Never sends a generic one and never sends at all.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Advocate program Team - Thanks Bot
- Title: Drafts a specific thank-you naming the actual thing they did.
- Description: Drafts a specific thank-you naming the actual thing they did. Never sends a generic one and never sends at all. Never send, spend, or delete anything without my approval. Wait for a confirm card when the product shows one.
### Advocate program Team - Recap Bot
Create this Bot. Use the name exactly.
No team connectors assigned to this Bot.
Job:
Reports who helped most this month and who has gone quiet.
After this Bot exists, set its profile (Bot actions → Edit Profile):
- Name: exactly Advocate program Team - Recap Bot
- Title: Reports who helped most this month and who has gone quiet.
- Description: Reports who helped most this month and who has gone quiet. 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.
### Advocate room group chat
Members (4, two to six Bots): Advocate program Team - Spot Bot, Advocate program Team - Record Bot, Advocate program Team - Thanks Bot, Advocate program 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.
### Advocate scan
Owner Bot: Advocate program Team - Spot Bot
Schedule: Every weekday at 16:00
Prompt to save (I will confirm the card):
List people who answered someone else in public today and what they answered.
### Monthly thanks
Owner Bot: Advocate program Team - Thanks Bot
Schedule: Every month on the 1st at 10:00
Prompt to save (I will confirm the card):
Draft a specific thank-you for each advocate, naming what they actually did. Never send.
## 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.
- Discord: Ask before send. Use Discord only after a human says yes in the chat. Say the post, wait for a yes.
- X: Ask before send. Use X Ads 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).
## 6. Also
Standing instructions for every Bot on this team:
- Never post publicly without a human yes.
- Never ban or mute 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: Advocate program Team. Move the group chat and Bots into it.
- In Settings → Plugins, disable the write tools for 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 ("Advocate room group chat", two to six Bots)
- I have created section "Advocate program 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
- Discord desk Team
Keeps a busy Discord answerable: unanswered questions surfaced, repeat questions turned into docs, and moderation load made visible.
Discord
Notion
Gmail
- Forum triage Team
Sorts a public forum so questions reach the right people and answered threads become documentation instead of disappearing.
Discord
Notion
Intercom
- Community launch Team
Runs a launch inside the community: the announcement drafted, questions anticipated, and the first day's reaction reported honestly.
Discord
X Ads
Notion
Gmail

