botteams.io

Grok Bot teams directory

botteams.io is a directory of teams and Bots you paste into Grok Bot. Each team is named Bots, a group chat, and routines.
Use them at work, in a business, or for everyday life. Copy one installer prompt. Nothing is installed on this site.

Grok Bot Teams

12 of 140 results

AgencyProject handover Team

Closes finished projects properly: final assets filed, client access reviewed, last invoice checked, and a retro written while people still remember.

  • Notion
  • Google Drive
  • Stripe
  • Gmail
5 Bots· 1 group chat· 2 routines
BookkeepingVAT and filings Team

Keeps filing deadlines and the numbers behind them in one place, so a return is never assembled the night before it is due.

  • Xero
  • Google Calendar
  • Gmail
  • Google Drive
4 Bots· 1 group chat· 2 routines
ContentEditorial standards Team

Reads drafts before a human editor does, catching claims without sources, house-style breaks, and the things that get fixed at the last minute.

  • Notion
  • Google Drive
  • Gmail
4 Bots· 1 group chat· 2 routines
Investor updatesData room Team

Keeps the data room current between raises, so diligence does not become a fire drill.

  • Google Drive
  • Notion
  • Xero
  • Docusign
4 Bots· 1 group chat· 2 routines
Investor updatesUpdate letter Team

Drafts the monthly letter with the bad news first, and tracks what was promised in the last one.

  • Notion
  • Gmail
  • Stripe
  • Google Drive
4 Bots· 1 group chat· 2 routines
KnowledgeOnboarding docs Team

Keeps the documents a new joiner actually reads in their first week correct, because those are the ones that mislead.

  • Notion
  • Glean
  • Google Drive
  • Slack
4 Bots· 1 group chat· 2 routines
KnowledgeFindability Team

Measures whether people can find what exists, and fixes the naming that stops them.

  • Glean
  • Notion
  • Google Drive
4 Bots· 1 group chat· 2 routines
SponsoredAgent Plugins DirectoryA ranked index of tools for coding agents.
LegalContract register Team

Keeps one list of what the company signed, what it committed to, and when each obligation lands.

  • Docusign
  • Notion
  • Google Drive
  • Google Calendar
4 Bots· 1 group chat· 2 routines
LegalPrivacy desk Team

Tracks what personal data the company holds, where it goes, and which requests are running out of time.

  • Notion
  • Gmail
  • Google Drive
  • Google Calendar
4 Bots· 1 group chat· 2 routines
ResearchResearch synthesis Team

Turns finished research into something people can actually use, and says when the answer is not known.

  • Notion
  • Glean
  • Google Drive
  • Gmail
4 Bots· 1 group chat· 2 routines
KnowledgeKnowledge base Team

Runs a knowledge base across four stores: stale pages found, duplicates named, records checked, and gaps in documentation reported.

  • Notion
  • Google Drive
  • Box
  • Airtable
  • Glean
5 Bots· 1 group chat· 3 routines
Investor updatesInvestor updates Team

Assembles the monthly investor update: numbers pulled from source, the letter drafted, questions tracked, and nothing invented.

  • Gmail
  • Google Calendar
  • Stripe
  • Notion
  • Google Drive
6 Bots· 1 group chat· 3 routines
How it works

Pick a team. Copy the installer prompt. Paste it into Grok Bot. The prompt creates named Bots and a group chat (two to six Bots), tells you to make a sidebar section, and pings each Bot so you can confirm routines. Connectors must already be on the account.

Questions
What is a Grok Bot team?
A named set of two to six Bots plus one group chat and standing routines. You paste one installer prompt into Grok Bot. Nothing is installed on this site.
How do I install one?
Open a team. Copy the installer prompt. Paste it into Grok Bot. Connect the connectors the team lists first. The prompt creates the Bots and the group chat on your account.
Is botteams.io affiliated with xAI?
No. Ellelion LLC operates this directory. From xAI on a Bot is sourcing from xAI's published use cases, not a certification.
Add a team

Every team here is one file. Front matter names the Bots, the group chat, the routines, and the connectors the account needs first. The installer prompt is generated from it, so the file is the product.

No GitHub needed: reply under a public X post that describes a Bot setup and tag @botteams_bot. The worker drafts an example pull request, and a maintainer reviews it before it appears here.