From browser-bridge
First-time Browser Bridge setup and post-install onboarding. Use when the user installs browser-bridge, runs /browser-bridge-setup, asks how to set up Chrome extension auth, needs the bridge token, or bridge_status shows extensionAuthenticated false. Triggers on "browser bridge setup", "install extension", "auth failed", "auth timeout", "connect browser bridge".
How this skill is triggered — by the user, by Claude, or both
Slash command
/browser-bridge:browser-bridge-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **MCP server** — exposes 29 browser tools to the agent (stdio via Grok, or HTTP gateway)
127.0.0.1:18793 (auto-started)extension/dist (not from Chrome Web Store)bash ${CLAUDE_PLUGIN_ROOT}/scripts/setup-token.sh
Stored at ${CLAUDE_PLUGIN_ROOT}/.bridge-token (gitignored). Copied to clipboard when wl-copy, xclip, or xsel is available.
cd ${CLAUDE_PLUGIN_ROOT} && bun install && bun run build:extension
chrome://extensions → Developer mode → Load unpacked → ${CLAUDE_PLUGIN_ROOT}/extension/distThe build injects the token into the background bundle. If auth fails:
chrome://extensions after rebuildbash ${CLAUDE_PLUGIN_ROOT}/scripts/setup-wizard.sh --check
Or use MCP bridge_status — need all three: bridgeReachable, extensionConnected, extensionAuthenticated.
Always:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/setup-token.sh (or --regenerate)bun run build:extensionstop-gateway.sh then start-gateway.shFor clients that need HTTP MCP instead of stdio:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/start-gateway.sh
# MCP endpoint: http://127.0.0.1:18794/mcp
/browser-bridge-setup command for the full walkthroughsetup-wizard.sh --check for programmatic healthlist_tabsnpx claudepluginhub awfixers-stuff/plugins --plugin browser-bridgeSets up isolated workspaces using native worktree tools or git worktree fallback. Use before starting feature work to protect the current branch.