Contribute

The repo is the admin panel.

Each bot is two files in data/entries/: a JSON file for the metadata and a markdown file for the instructions. The submit form drafts both for you. Full spec: CONTRIBUTING.md.

House rules

Instructions are the point

The markdown file holds the bot's actual prompt, and it is required for every bot whose prompt you can publish. The one exemption is a native x.ai share link, where the prompt stays behind the link and is not yours to copy: set instructions to null there.

Only submit instructions you wrote or that are licensed for redistribution, and record the licence in the license field. If it is CC-BY, the author goes in author, because that is a legal requirement and not a courtesy.

Two ways to add

Categories

Pick exactly one. Closed list; adding to it is its own pull request.

Integrations

Exact spellings, and only the tools the bot genuinely needs. Closed for the same reason.

Slack · Gmail · Google Calendar · Google Docs · Google Drive · Google Search Console · GitHub · Notion · LinkedIn · X · Stripe · Reddit

An example

data/entries/inbox-triage.json

{
  "slug": "inbox-triage",
  "name": "Inbox Triage",
  "category": "productivity",
  "tagline": "Sorts the morning inbox into reply, read, and ignore.",
  "description": "Reads unread Gmail, groups by what it wants from you, and drafts the easy replies.",
  "integrations": [
    "Gmail"
  ],
  "add": {
    "kind": "profile-url",
    "url": "https://raw.githubusercontent.com/you/your-repo/main/bots/inbox-triage/SETUP.md",
    "hint": null
  },
  "instructions": "inbox-triage.md",
  "source": "https://github.com/you/your-repo/blob/main/bots/inbox-triage/PROFILE.md",
  "homepage": null,
  "license": "CC0-1.0",
  "author": "you",
  "tags": [
    "email",
    "triage"
  ],
  "verified": false,
  "added": "2026-08-28",
  "notes": null
}

With data/entries/inbox-triage.md beside it holding the prompt, as plain markdown, no frontmatter.