Fields
$schema | Optional editor hint. Use https://botteams.io/schema/team.schema.json. |
|---|---|
slug | Lowercase URL key. Must equal the markdown filename. |
name | Team title on the directory. |
tagline | One line for the job of the team. |
bots | Count of Bots in the recipe. Must match the bot_roster list length. |
section | Closed directory category. On a team, it is also the suggested sidebar section. |
kind | team (two to six Bots and a group chat) or bot (one Bot and no group chat). |
status | installable (ready to run) or example (format demo). |
connectors | Account-wide connectors this team expects already connected. Union of per-Bot lists. |
Bot roster bot_roster | Each Bot: name + persona (the job). Optional icon, connectors (subset of the team list), reuse. |
Group chats rooms | Each group chat: name + members (Bot names). Visible label is Group chat. |
routines | name, owner Bot, schedule, prompt. A routine is owned by one Bot. |
skills | Optional. Named later. Skills cannot be attached at Bot create time. |
Published limits we map to
- Bot definition: In the Docs and in the Grok Bot app, a Bot is one persistent, named AI teammate.
- A Bot has a name, a job, its own conversation, and working context. Create it from Grok Bot, then edit its profile: name, title, description, and avatar. Cited from the Bots doc.
- Group chat is created by selecting two to six Bots.
- Account cap: 50 Bots and group chats combined, from the Bots doc.
- A routine tells one Bot when to run a workflow. One Bot can own up to 50 routines, and Grok Bot keeps the 20 most recent runs of each. There is no documented cap on a team as a whole, so this directory does not invent one.
Two shapes
A bot is one Bot doing one job. A team is two to six Bots in one group chat. They are different files in different folders, and the directory never adds them up into a single count, because a recipe with no group chat is not a team.
| Field | bots/ | teams/ |
|---|---|---|
kind | bot | team |
bots | Always 1 | 2 to 6, matching bot_roster |
bot_roster | Exactly one Bot | Two to six Bots |
rooms | Forbidden. Empty or absent | Required. Each holds 2 to 6 Bots |
routines | 0 to 50 per owning Bot | 0 to 50 per owning Bot |
| Verified | Never | When the roster fits the limits |
| URL | /bots/<slug> | /teams/<slug> |
From xAI
A From xAI chip means the job is our write-up of one xAI publishes in its Grok Bot use-case gallery. It is sourcing and nothing more. It is not a certification, it is not Verified, and xAI does not review or endorse anything on this directory. The title and the category are theirs. The Bot, the connectors, the modes and the standing instructions are ours.
Verified
Verified exists for teams only. A team is Verified when it has at least one group chat, every group chat holds two to six Bots, the Bot count matches the roster, and Bots plus group chats stay under the account cap of 50.
A bot is never Verified. That is not a downgrade: Verified is a claim about a group chat, and a recipe with one Bot does not make one. An empty roster used to slip past this check, which is how 56 one-Bot recipes were once counted as teams.
Install notes
A team is one markdown file under teams/, and a bot is one under bots/, both with YAML frontmatter. GitHub is the CMS. There are no accounts and no connector API on this site.
A bot installer creates one Bot and its routines. It never asks for a group chat or a sidebar section, because neither means anything for a single Bot.
Sidebar sections are a human action. In Grok Bot, use Move to, then New section, and name the section exactly as the team lists it.
Skills cannot be attached at Bot create time. A team may point at references such as the stripe-best-practices skill on Skillselion or a plugin in the Agent Plugins Directory. Those are named destinations the team expects, not installs this site performs.
Uninstall is sidebar delete. Remove the Bots and group chats in Grok Bot. There is no remote uninstall from botteams.io.
