geekbot-status
Geekbot — Status
Goal: emit a compact health check for the CLI. Useful both as a user-triggered /geekbot:geekbot-status and as a pre-flight check before any action skill that shells out to geekbot.
Steps
-
Locate the binary:
command -v geekbot -
If found, capture its version:
geekbot --version -
Check auth state (JSON):
geekbot auth status
Output
A single compact markdown table. Report only what was checked — no "next step" row.
| Check | Value |
|---|---|
| Binary | /home/user/.nvm/versions/node/vX/bin/geekbot |
| Version | 0.2.4 |
| Authenticated | yes (sabpap@geekbot.com) |
If the binary is missing, show Binary: not installed and leave Version/Authenticated blank.
If the binary exists but auth is missing, show Authenticated: no.
Keep it to the table — no prose about remediation.
Failure recovery (only when status or an action skill fails)
This guidance applies when /geekbot:geekbot-status, the main action skill, or any geekbot-dependent flow hits a blocker — not as part of the status table itself.
- Binary missing → recommend running
/geekbot:geekbot-setup. - Auth missing or invalid → recommend running
/geekbot:geekbot-setup.
Surface the recommendation as a short follow-up line after the failure, e.g. "Run /geekbot:geekbot-setup to install and authenticate the CLI."