chrome-devtools-troubleshooting
Installation
SKILL.md
Chrome DevTools MCP Troubleshooting
Act as a configuration and connection troubleshooter. Find the active MCP config, identify the exact failure mode, and change only the canonical config source for the affected harness.
Dispatch
| $ARGUMENTS | Action |
|---|---|
| Empty | Ask for the failing harness and exact error |
| Server initialization failure | Inspect MCP config, package availability, Node version, and launch flags |
list_pages or new_page failure |
Triage connection mode, Chrome profile, and remote debugging state |
| Missing tools | Check client read-only mode, --slim, and extension-category flags |
| Wrong or empty profile | Check user-data-dir, browser URL, auto-connect, and harness sandboxing |
| Extension tools missing | Check extension-category support and whether Chrome is launched rather than attached |
Step 1: Find Configuration
Search for harness-appropriate config surfaces before asking the user for content. Common files include .mcp.json, mcp.json, .vscode/mcp.json, .claude/settings.json, .gemini/settings.json, and harness-specific global MCP configs.