Menu
Use when a tool call fails with "extension not connected", the daemon is unreachable, or browser telemetry stops arriving.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot", "browser errors", "network requests", "automate the browser", "record a test", "accessibility audit", "performance check", "what's on the page".
Use when the user wants a full Kaboom quality audit of a web app or tracked site, with one polished report covering Functionality, UX Polish, Accessibility, Performance, Release Risk, and SEO.
Use when user says "QA my app", "find all bugs", "check my app for problems", "debug my whole app", "what's broken", or wants a comprehensive quality review of their web application.
Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift.
Use when user asks to automate browser actions, click buttons, fill forms, navigate pages, run a sequence of browser steps, or build a repeatable workflow.
Use when MCP tools fail to connect, user reports "extension not connected", tool calls return errors, or user asks to check their Kaboom setup.
| name | kaboom-connection-guard |
| description | Use when a tool call fails with "extension not connected", the daemon is unreachable, or browser telemetry stops arriving. |
| auto-trigger | [{"on-error-pattern":"extension not connected"},{"on-error-pattern":"no tracked tab"},{"on-error-pattern":"connection refused"},{"on-error-pattern":"daemon not running"},{"on-error-pattern":"ECONNREFUSED"},{"on-error-pattern":"no active connection"}] |
| allowed-tools | ["mcp__kaboom__configure"] |
This skill activates automatically when a Kaboom MCP tool call fails with a connection-related error. It diagnoses the problem and guides the user through recovery.
Any Kaboom tool call (observe, analyze, generate, interact, configure) returns an error matching:
Classify the error into one of these categories:
| Error Pattern | Diagnosis | Likely Cause |
|---|---|---|
| "daemon not running" / "ECONNREFUSED" | Daemon Down | Kaboom MCP server process is not running |
| "extension not connected" / "no active connection" | Extension Disconnected | Chrome extension lost its WebSocket connection to the daemon |
| "no tracked tab" | No Tracked Tab | Extension is connected but no tab is being monitored |
Attempt configure with what: "health".
If health check succeeds: The daemon is running. The issue is likely transient or tab-specific. Report the health status and suggest the user retry their command.
If health check fails with connection refused: The daemon is not running. Proceed to Step 3.
If health check returns but shows extension disconnected: The daemon is running but the extension is not connected. Proceed to Step 4.
Tell the user:
The Kaboom daemon is not running.
To fix this:
1. Check if the process is alive: `ps aux | grep kaboom`
2. Restart the daemon — it should auto-start when Claude Code calls a Kaboom tool
3. If it doesn't auto-start, run `kaboom-agentic-browser` manually to see any startup errors
Common causes:
- Port conflict (another process on the daemon port)
- Crashed due to an unhandled error (check recent logs)
- Not installed or not in PATH
After the user reports the daemon is back, run the health check again to verify.
Tell the user:
The Kaboom daemon is running but the Chrome extension is not connected.
To fix this:
1. Open Chrome and check the Kaboom extension icon — it should show a green indicator when connected
2. Click the extension icon and verify the connection status
3. If disconnected, try:
- Refresh the page you're working on
- Click "Reconnect" in the extension popup (if available)
- Disable and re-enable the extension in chrome://extensions
- Close and reopen Chrome as a last resort
If the extension shows "connected" but tools still fail, the tracked tab may have been closed.
After the user reports the extension is reconnected, run the health check again to verify.
Tell the user:
The extension is connected but no tab is being tracked.
To fix this:
1. Open the page you want to work with in Chrome
2. Click the Kaboom extension icon on that tab
3. Enable tracking for the tab (toggle or click "Track this tab")
The extension needs an active tracked tab to capture browser telemetry.
After the user reports a tab is tracked, run the health check again to verify.
After any recovery step, run configure with what: "health" one final time.
If healthy: Tell the user the connection is restored and they can retry their original command.
If still failing: Report the persistent failure and suggest checking the Kaboom GitHub issues or logs for more information.