grok-botlisted

Chat with Grok Bot teammates, message a named Grok Bot, create a new Grok Bot, list Grok Bots, read a Grok Bot transcript, or operate the xAI Grok Bot desktop app from Cursor, Claude Code, or Codex instead of the UI. Use when the user mentions Grok Bot, Grok teammates, Reed, Agent Computer, spinning up a new bot, or talking to Grok from the terminal.
adamanz/grok-bot-skill · ★ 0 · AI & Automation · score 75

Install: claude install-skill adamanz/grok-bot-skill

# Grok Bot Talk to existing Grok Bot teammates and create new ones through the local CLI. Do not drive the Grok Bot desktop UI and do not call the gateway by hand. ## Workflow 1. Run `status`, then `list`. 2. Message an existing bot with `chat` (waits for a reply) or `send` (fire-and-forget). 3. Create a new bot with `create` only when the user asked for a new teammate. 4. Prefer one focused job per bot. Put standing rules in `--description`. Keep first tasks draft-only. The CLI is `scripts/grokbot.py` next to this file. Resolve that path from the installed skill directory (often `~/.cursor/skills/grok-bot/scripts/grokbot.py`). ```bash SCRIPT="$(dirname "$0")/scripts/grokbot.py" # or, after a global Cursor install: SCRIPT="$HOME/.cursor/skills/grok-bot/scripts/grokbot.py" python3 "$SCRIPT" status python3 "$SCRIPT" list python3 "$SCRIPT" chat --name Reed --prompt "What are you waiting on from me?" python3 "$SCRIPT" create --name Reed --title "Chief of staff" --description "Draft-only daily brief. Never send messages." python3 "$SCRIPT" transcript --name Reed --limit 20 ``` Output is JSON. Summarize it for the user. Never paste tokens, gateway URLs, or raw keychain material into chat. ## Create rules A new bot needs: - `--name` — short, unique - `--title` — one job, not "general helper" - `--description` — outcome, sources, and what it must not do without approval Do not create a second bot with the same name unless the user asks. The CLI refuses duplicates unless `-