troubleshooting
Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
87
83%
Does it follow best practices?
Impact
95%
1.58xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Evaluation results
100%
53%Chrome DevTools MCP: Connection Failure on macOS
DevToolsActivePort error sequence
Chrome version confirmation first
66%
100%
Specific remote debugging URL
0%
100%
Enable remote debugging checkbox
0%
100%
list_pages as verification step
0%
100%
--browserUrl deferred
100%
100%
Ordered escalation
20%
100%
Config file read
100%
100%
No premature --browserUrl
100%
100%
100%
10%Incomplete Tool Set in Chrome DevTools MCP Integration
Read-only mode limited tools diagnosis
Read-only mode identified
100%
100%
readOnlyHint mechanism explained
100%
100%
readOnlyHint:true tools visible
100%
100%
readOnlyHint:false tools suppressed
100%
100%
Gemini Plan Mode identified
80%
100%
Resolution: disable read-only
100%
100%
Tool safety settings mentioned
0%
100%
Not a server/installation issue
100%
100%
Server working correctly noted
100%
100%
Specific visible tools cited
100%
100%
87%
44%Setting Up Chrome DevTools MCP for a Sandboxed AI Assistant Environment
Sandbox config and diagnostic commands
--browser-url used
0%
100%
--autoConnect absent
100%
100%
Help command present
53%
100%
DEBUG verbose command
0%
80%
Absolute log file path
0%
100%
Config file search before asking
100%
0%
Remote debugging instruction
100%
100%
- Repository
- ChromeDevTools/chrome-devtools-mcp
- Commit
1b857c9
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.