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.
86
83%
Does it follow best practices?
Impact
90%
1.42xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Evaluation results
95%
59%Chrome DevTools MCP Connection Failure
DevToolsActivePort error sequence
Config file referenced
75%
100%
Reads troubleshooting docs
0%
37%
Error correctly identified
100%
100%
Step 1: Confirm Chrome running
25%
100%
Step 2: Enable remote debugging
0%
100%
Step 3: Test with list_pages
0%
100%
browserUrl not first solution
100%
100%
browserUrl as fallback only
41%
100%
logFile suggestion
0%
100%
Correct step ordering
25%
100%
84%
14%Investigating Limited Browser Automation Capabilities
Read-only mode missing tools diagnosis
Config file read
100%
100%
Read-only mode identified
85%
100%
readOnlyHint explained
100%
100%
Client-side fix recommended
92%
100%
Server NOT blamed
90%
100%
Reads troubleshooting docs
0%
0%
Diagnostic command: --help
100%
100%
Diagnostic command: DEBUG verbose
0%
100%
GitHub issue search
0%
0%
Affected tools named
100%
100%
93%
10%Browser Extension Automation Not Working
Extension tools unavailable diagnosis
Config file read
100%
100%
--categoryExtensions flag identified
100%
100%
Chrome 149 version requirement
100%
100%
Connecting mode limitation explained
100%
100%
Server-launch mode recommended
100%
100%
Reads troubleshooting docs
37%
12%
GitHub issue search with gh CLI
0%
100%
GitHub issues/discussions URL fallback
100%
100%
Exact flag syntax provided
100%
100%
- Repository
- ChromeDevTools/chrome-devtools-mcp
- Commit
faac61d
- 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.