When Chrome DevTools MCP connections fail, this skill walks you through the diagnostic process systematically. It starts by hunting down your config files, then triages common errors like "Could not find DevToolsActivePort" with specific fix sequences. The approach is methodical: confirm Chrome is running, verify remote debugging is enabled at chrome://inspect, then test with list_pages before anything fancy. It knows the difference between a typo in autoConnect and actual sandboxing issues, catches when you're stuck in read-only mode with only 9 tools available, and will check the troubleshooting docs or GitHub issues if needed. Basically a runbook that stops you from randomly tweaking flags when your browser automation breaks.
npx skills add https://github.com/chromedevtools/chrome-devtools-mcp --skill troubleshooting