Stats
Actions
Tags
From browzer
Pre-flight probe for any Browzer agent loop — confirms login, workspace binding, gateway/organization via `browzer status`. Use first in any session before explore/search/sync; for install/login itself use `use-rag-cli`. Triggers: browzer status, browzer pre-flight, browzer auth check, browzer context, browzer health check, browzer diagnose, BROWZER_SERVER check, 'am I logged in to browzer', 'which browzer workspace', 'what server is browzer pointing at'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/browzer:auth-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The cheapest call in the entire `browzer` CLI. Always run it before doing anything else with Browzer in a session: it tells you whether the user is authenticated, which server the CLI is pointing at, and which workspace the current directory is bound to.
The cheapest call in the entire browzer CLI. Always run it before doing anything else with Browzer in a session: it tells you whether the user is authenticated, which server the CLI is pointing at, and which workspace the current directory is bound to.
This skill is probe-only. For installing the CLI or running browzer login itself, use use-rag-cli.
browzer status --json
browzer status --json --save /tmp/status.json
The first form emits JSON to stdout. The second saves to a file — preferred in agent loops.
Then Read /tmp/status.json and branch:
explore-workspace-graphs / semantic-search / embed-workspace-graphs / embed-documents.embed-workspace-graphs (browzer init) or workspace-management (browzer workspace list + relink).2) → run use-rag-cli (browzer login).Why probe before every chain: Browzer state can drift mid-session (token expiry, server URL change, workspace deleted in another tab). A 50ms probe upfront prevents a 60s ingestion job from failing on auth.
exit 2 → not authenticated; run use-rag-cli (browzer login). This skill diagnoses the problem; use-rag-cli fixes it.explore-workspace-graphs returns nothing → browzer workspace index hasn't run yet; see embed-workspace-graphs.BROWZER_SERVER env var is set somewhere unexpected; unset and re-login.SessionStart hook already runs browzer status --json automatically — the result is in your context at boot. Re-run it explicitly only when state may have changed.--json or --save; never parse the human-formatted variant.Emit the skill emits ONE line summarising the probe:
Authenticated + workspace bound: auth-status: <email> on <workspace> (<chunks-used>/<chunks-limit> chunks, <server-label>)
Authenticated, no workspace bound: auth-status: <email> authenticated; ⚠ no workspace bound to this directory — run embed-workspace-graphs
Not authenticated (exit 2): two lines per the failure contract:
auth-status: failed — not authenticated (exit code 2)
hint: run use-rag-cli (browzer login)
Never dump /tmp/status.json body in chat — cite the path if the operator needs detail.
npx claudepluginhub browzeremb/skills --plugin browzerGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.