Front door that triages work, absorbs routine admin, and routes the rest to named specialists
What this Grok bot does
Chief of Staff front door for a specialist swarm. Triages priorities, cuts boring admin, and routes work to the right teammate — stays outer loop, never the specialist.
Ops at a glance
Ops is an on demand life bot shared by @Rimusz and first listed on 2026-09-20. It works when you message it rather than on a timer, which keeps usage low. 4 independent public catalogs list it, and its x.ai share link was last checked live on 2026-10-20.
How Ops compares
On our popularity score (installs, votes and how many catalogs list it), Ops shares rank 569 of 3,304 Personal & Life bots with 717 others. @Rimusz has shared 2 bots here, all of them life bots.
| Bot | What it does | Schedule · access | Compared with Ops |
|---|---|---|---|
| atr Operator@Rimusz | Front door to atr | On demandLow access | Both cover front, door and work. It comes from the same creator. |
| Nero · CEO / SPOT@OHB_Honeybadger | Single front door Chief of Staff for a small Grok Bot team | On demandConnects accounts | Both cover front, door and specialists. It asks for more access (code repos). |
| CAO@Shadygday | Chief Agent Officer | On demandLow access | Both cover routes, work and specialists. Same schedule and access level. |
Access and permissions
Low access Its public description does not mention connecting accounts, so you can try it in chat without granting access to anything.
No account access mentioned in the public description.
Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.
Before you add Ops
- Start with a bot that needs no integrations, then add access one account at a time.
- Open the x.ai page and read the full instructions, skills and routines it ships with.
Adding a template gives you an independent copy — never the creator's chats, sessions or keys. How adding a Grok Bot template works.
2 other Grok bots named “Ops”
Different creators, different bots — compare what each one does before you pick.
- Ops by Alex — Keeps a multi-bot team's playbook current and spots stuck or wasteful bots and routines.
- Ops by @jason_bennitt — Keeps a fleet of AI assistants healthy. Audits routines, handoffs, skills, rooms and each bot's purpose, fixes what's safe.
More from @Rimusz
atr Operator
@Rimusz
Front door to atr: queue coding work onto the CLIs you already pay for, watch status and usage, and bring PRs and answers back.