From geekbot
Installs, authenticates, and verifies the geekbot CLI end-to-end via OAuth loopback flow with no manual token entry.
How this skill is triggered — by the user, by Claude, or both
Slash command
/geekbot:geekbot-setupThis 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: get the user fully ready — CLI installed, CLI authenticated, and a clear "you're ready" or "here's what to do next" message at the end.
Goal: get the user fully ready — CLI installed, CLI authenticated, and a clear "you're ready" or "here's what to do next" message at the end.
Check the CLI is on $PATH:
command -v geekbot
Install if missing:
npm install -g geekbot-cli
If npm isn't available, mention bun install -g geekbot-cli as an alternative and let the user run it themselves.
Verify the install:
geekbot --version
Check auth (does not prompt):
geekbot auth status
data.authenticated == true → skip to step 6.Authenticate via OAuth — you drive geekbot auth login yourself.
Do NOT tell the user to run anything in their shell. Do NOT ask for an
API key. The CLI's loopback flow only exposes a public authorize URL
(no secrets), and writes the resulting cli_* token to the user's OS
keychain on their own machine when the flow completes.
Procedure:
a. Start the login command in the background. Use Bash with
run_in_background: true so you can read the verification URL while
the CLI waits on its loopback listener. Always pass --no-browser —
you can't pick the user's browser for them, especially on WSL where
xdg-open would launch the Linux default rather than the browser
that holds the user's Geekbot dashboard session.
geekbot auth login --no-browser --ttl-days 30
b. Capture the authorize URL. Call BashOutput on the background
shell once, then again a second later if needed, until stderr
contains a line that starts with https:// and a URL pointing at
/v2/authorize?.... The CLI prints a block like:
Listening on http://127.0.0.1:<port>/callback for the OAuth callback…
Open this URL in a browser to sign in:
https://oauth.geekbot.com/v2/authorize?...&state=...&code_challenge=...
Only open it ONCE — the state is single-use.
c. Show the URL to the user, exactly once. Reply with something like:
To finish signing in to Geekbot, open this URL in any browser you're already logged into your dashboard with:
<URL>Only open it once — the OAuth
stateis single-use, so a second browser will fail.
d. Wait for the command to exit. Continue calling BashOutput
periodically until the background shell completes. Don't pre-empt
with a timeout shorter than the CLI's own (~5 min).
e. Parse the outcome:
{"ok": true, "data": {"authenticated": true, "method": "oauth_loopback", "username": ..., "email": ...}}.
Proceed to step 6.oauth_callback_timeout — user didn't click in time. Offer to
retry from step 5a.oauth_access_denied — user clicked "Cancel" at the IdP.oauth_state_mismatch / oauth_invalid_request — they opened
the URL twice; retry, remind them once is enough.oauth_invalid_client — the CLI's client_id isn't registered
on the auth server; this is an environment issue, not a user
one — report it and stop.Fallback only — do NOT suggest unless OAuth login fails twice in a row or the user explicitly asks for it. Long-lived dashboard API keys still work via:
! geekbot auth setup --api-key <YOUR_KEY>Report final state. Example:
geekbot CLI: installed (v0.2.4)
Auth: authenticated as [email protected] (oauth_loopback)
Next: you're ready — try "fetch my standups"
If auth is still missing, end with "run /geekbot:geekbot-setup again after completing the geekbot auth login step."
API keys and CLI tokens are secrets. Pasting one into the conversation puts it
in the transcript and any logs/exports derived from it. The CLI's auth login
flow keeps the token on the user's machine end-to-end: the auth server hands
it to the local CLI, which writes it straight to the OS keychain. Once stored,
every later geekbot … call authenticates silently.
npx claudepluginhub geekbot-com/geekbot-cli --plugin geekbotReports whether the Geekbot CLI is installed, its version, and authentication status in a compact table.
Guides GitHub CLI (gh) authentication setup via browser login, status checks, and troubleshooting auth errors, scopes, or updates.
Installs Google Workspace CLI (gws) on new machines using existing client_secret.json OAuth credentials. Covers npm install, credential import, and multi-scope browser auth.