From geekbot
Reports whether the Geekbot CLI is installed, its version, and authentication status in a compact table.
How this skill is triggered — by the user, by Claude, or both
Slash command
/geekbot:geekbot-statusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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`.
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.
Locate the binary:
command -v geekbot
If found, capture its version:
geekbot --version
Check auth state (JSON):
geekbot auth status
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 ([email protected]) |
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.
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.
/geekbot:geekbot-setup./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."
npx claudepluginhub geekbot-com/geekbot-cli --plugin geekbotInstalls, authenticates, and verifies the geekbot CLI end-to-end via OAuth loopback flow with no manual token entry.
Checks if the bopen-tools plugin is up to date by comparing local and GitHub versions. Returns status (current, outdated, etc.) and suggests update commands. Fast (~70ms).