Contributing to Awesome Grok Bot

August 23, 2026 · View on GitHub

Thanks for considering a contribution. Grok Bot is a days-old product with an ecosystem forming in real time, so we're strict about verification but fast about merging — target under 7 days to a first response on every PR.

Entries from ZeroPointRepo

No entry in this list is built by ZeroPointRepo yet. Nothing we ship has a working Grok Bot skill, plugin, or MCP integration at the time of writing, so nothing of ours is listed. If one lands, it is held to the same rules as every other entry, and to a higher bar on one point:

  • Same entry format as everyone else. No bold, no emoji, no "featured" styling, placed alphabetically.
  • At most one per category.
  • A higher acceptance bar: no working install path, no real README, it does not go in.
  • A competing entry is never rejected or downranked to protect one of ours.

Adding an entry

Open a PR that adds one line, in the right category, alphabetically, in this exact format:

- [name](repo-url) by [author](author-url) — one-line description. **[tag]**
  • tag — one of production, beta, experimental, or guide (docs/notes, not something you run).
  • Description: plain, one line, say what it does, not why it's great.

Acceptance bar (we merge if all four are true)

  1. The link resolves and the repo isn't empty or archived.
  2. It's genuinely about Grok Bot (xAI + Cursor's cloud-computer product, launched 2026-08-11) — not Grok Build, not a same-named-coincidence Telegram/Discord bot, not the ordinary Grok chat assistant.
  3. It's not already listed.
  4. The category is right. If it spans two, pick the primary use case — maintainers will move it rather than bounce the PR.

We reject only for: dead link, no real substance (empty/stub repo), pure spam, or exact duplicate. We always reply, even to a rejection.

Given how new this ecosystem is

Expect real churn — repos will go stale, get renamed, or get superseded within weeks as xAI/Cursor ship more official surface area. If you spot that happening, a "report broken entry" issue is exactly the right move, not something to hesitate over.

Style

  • One entry per line, no sub-bullets.
  • No affiliate links, no UTM parameters, no tracking redirects.
  • Keep descriptions under ~120 characters where you can.