Third-party tool
grok-bot-skill
What job it does
Let Cursor or Claude coding agents call your Grok Bot teammates as collaborators — hand off research, browser work, or ops tasks while you stay in the coding agent loop.
Platforms
Environments where a coding agent (Cursor / Claude-style) can load skills and where a signed-in Grok Bot session is available per the repo’s instructions.
Install
Install as a skill from adamanz/grok-bot-skill following the README. Confirm the permission scope the skill requests before enabling it in an agent that can write code or run tools. Keep the official Grok Bot desktop/phone for approvals that still need a human.
How it differs from the official app
This is not an official xAI/Cursor API. It wires coding agents to Grok Bot teammates; it is not a TUI, not a usage meter, and not Grok Build. Prefer official connectors and in-app approvals for anything that sends mail, spends money, or changes production.
What the skill can and cannot do
Treat grok-bot-skill as a bridge so a coding agent can list teammates, send a message, or create a Bot the way you would type it. Typical jobs: hand a research or browser task to a named Bot, then read the reply back in Cursor. It does not open Agent Computer, does not Take Over for passwords or 2FA, does not show the secrets card, and does not replace Require Approval. Teach a task, routines, plugin OAuth, Recover, and Reset stay in the official app. If the agent would send mail, spend money, or change production, stop and do that click where you can watch the computer.
Coding agent, official app, and CLI
This is not an official xAI or Cursor API and not a Grok Build skill. grok-bot-cli is for a human at a terminal on a signed-in Mac. grok-bot-skill is for a coding agent that can load skills. Official connectors (Gmail, GitHub, X) still belong on the Cursor account: install them in the Bot app or Cursor marketplace, not by pasting a skill.md that embeds tokens. If both a skill and a connector can do the job, prefer the connector. Do not clone this repo onto the Bot computer.
Approvals and weekly usage still apply
Messages and computer-use the skill triggers still count as Grok Bot work on the same Cursor weekly pool. A chatty agent that pings the Chief of Staff every turn will burn the week the same way a chatty CoS thread does. The skill will not warn you that the pool is empty or that On-Demand is about to start. Keep Require Approval in the official client. Strip secrets from any skill file before you commit or share it. Read the upstream README for the current tool list before you let an agent create Bots unattended.
Risks
Third-party skill. Sharing agent configs can leak secrets embedded in skill text. Strip credentials before publishing. Session/local access patterns depend on how you wire it — assume it can trigger real Bot actions that consume weekly usage.
License and source
License. As declared in the upstream repository README
Open GitHub source Prefer official install Symptom-based fixes
Third-party tools can touch a local session. They do not replace Require Approval, secrets cards, or Recover/Update in the official desktop app.