From geekbot
Reports geekbot CLI binary location, version, and authentication status in a compact markdown table. Safe proactive check before Geekbot actions.
npx claudepluginhub geekbot-com/geekbot-cli --plugin geekbotThis skill is limited to using the following tools:
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`.
Installs, authenticates, and verifies geekbot CLI end-to-end: checks PATH, npm/bun install, secure auth guidance via OS keychain, status report. Triggered via /geekbot:geekbot-setup.
Checks bopen-tools plugin version against GitHub in ~70ms, returning JSON status (current/outdated/ahead). Use at session start, for update queries, or suspicious skill behavior.
Diagnoses and auto-fixes Discord bot gateway connectivity, OAuth token expiration, and legacy Clawdis config issues. Checks Discord app status, process, HTTP endpoint, bot health, and recent activity.
Share bugs, ideas, or general feedback.
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 (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.
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."