← ClaudeAtlas

chrome-devtools-debugginglisted

Debug and analyze web applications using Chrome DevTools MCP. Use for console log inspection, network request monitoring, performance analysis, and debugging authenticated sessions. For basic browser automation (screenshots, form filling), use browser-discovery skill instead.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 79
Install: claude install-skill aiskillstore/marketplace
# Chrome DevTools Debugging Debug web applications by connecting to Chrome's DevTools Protocol. This skill enables: - **Console inspection**: View errors, warnings, and log messages - **Network analysis**: Monitor XHR/fetch requests with full headers/body - **Performance tracing**: Record and analyze performance traces - **JavaScript evaluation**: Execute code in browser context - **Authenticated session debugging**: Connect to existing logged-in browsers ## When to Use This Skill | Use Case | This Skill | browser-discovery | |----------|------------|-------------------| | Console error inspection | Yes | No | | Network request analysis | Yes | Limited | | Performance tracing | Yes | No | | Authenticated sessions | Yes | No | | Screenshots | No | Yes | | Form filling | No | Yes | | Basic navigation | Limited | Yes | ## Setup Requirements ### Option 1: Connect to Existing Chrome (Recommended) Start Chrome with remote debugging enabled: ```bash # Linux google-chrome --remote-debugging-port=9222 # macOS /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 # Windows "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 ``` Set the environment variable: ```bash export CHROME_DEVTOOLS_URL=http://127.0.0.1:9222 ``` ### Option 2: Chrome Auto-Connect (145+) For Chrome 145+, enable remote debugging at `chrome://inspect/#remote-debugging`. ## Progressive Disclosure Pattern This skill uses **progressive M