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
—
Does it follow best practices?
Impact
90%
1.52xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
DevToolsActivePort error diagnostic sequence
Config file read first
100%
100%
Identifies autoConnect
100%
100%
Chrome version check step
50%
100%
Remote debugging URL
100%
100%
list_pages as verifier
0%
100%
No premature browserUrl
100%
100%
Advanced steps conditional
100%
100%
Troubleshooting doc referenced
12%
100%
logFile suggestion
0%
100%
Correct sequence ordering
21%
100%
Missing tools and empty profile diagnosis
Config file located first
100%
100%
Flag typo identified
100%
100%
Corrected flag provided
100%
100%
Read-only mode diagnosis
0%
100%
readOnlyHint explanation
0%
100%
Plan Mode / read-only disable
0%
100%
Corrected config provided
100%
100%
Troubleshooting doc referenced
0%
100%
No slim flag blame
100%
100%
npx help command mentioned
100%
0%
Extension tools missing and protocol timeout investigation
Config read first
100%
100%
categoryExtensions flag identified
100%
100%
Launch vs connect limitation
100%
100%
browserUrl limitation noted
100%
100%
Troubleshooting doc consulted
0%
40%
GitHub issue search performed
0%
0%
gh CLI command shown
0%
0%
Verbose debug command
100%
100%
logFile absolute path
100%
100%
Updated config provided
100%
100%
npx help command
0%
100%
e5bd334
Table of Contents
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.