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.

1.42x

Quality

83%

Does it follow best practices?

Impact

90%

1.42x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Discovery

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-constructed skill description with excellent trigger terms and completeness. It clearly identifies both what the skill does and when to use it with specific function names as triggers. The main weakness is that the 'what' portion could be more specific about the concrete troubleshooting actions performed rather than just saying 'troubleshoot.'

Suggestions

Add specific troubleshooting actions to improve specificity, e.g., 'diagnoses port conflicts, verifies Chrome launch flags, checks target availability, and resolves WebSocket connection errors.'

Dimension	Reasoning	Score
Specificity	Names the domain (Chrome DevTools MCP troubleshooting) and some actions (troubleshoot connection and target issues), but doesn't list specific concrete troubleshooting steps or resolution actions beyond the general 'troubleshoot' verb.	2 / 3
Completeness	Clearly answers both 'what' (uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues) and 'when' (explicit trigger clause: when list_pages, new_page, or navigate_page fail, or when server initialization fails).	3 / 3
Trigger Term Quality	Includes highly specific and natural trigger terms: 'list_pages', 'new_page', 'navigate_page', 'server initialization fails', 'Chrome DevTools MCP'. These are exactly the terms a user or Claude would encounter when hitting these errors.	3 / 3
Distinctiveness Conflict Risk	Very specific niche — Chrome DevTools MCP troubleshooting with named function failures. Unlikely to conflict with other skills due to the highly specific tool names and failure scenarios mentioned.	3 / 3
	Total	11 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong troubleshooting skill with excellent actionability and workflow clarity. The step-by-step diagnostic process is well-sequenced with clear validation checkpoints and feedback loops, particularly for the DevToolsActivePort error. Minor improvements could be made in conciseness (trimming the preamble and some explanatory text) and progressive disclosure (splitting detailed error patterns into referenced files).

Suggestions

Remove the opening paragraph ('You are acting as a troubleshooting wizard...') as it restates the skill description and wastes tokens on framing Claude already understands from the trigger context.

Consider extracting the detailed error patterns in Step 2 into a separate ERRORS.md reference file, keeping only a summary table in the main skill with links to detailed guidance.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and domain-specific, but includes some unnecessary framing ('You are acting as a troubleshooting wizard') and could be tightened in places. The detailed error-specific guidance is valuable and not something Claude would inherently know, but some sections are slightly verbose.	2 / 3
Actionability	The skill provides highly concrete, actionable guidance: specific URLs to navigate (chrome://inspect/#remote-debugging), exact CLI commands (npx chrome-devtools-mcp@latest --help, DEBUG=* npx...), specific flag names to check, and exact tool calls to verify fixes (list_pages). The troubleshooting steps are copy-paste ready.	3 / 3
Workflow Clarity	The 6-step diagnostic process is clearly sequenced with explicit validation checkpoints. Step 2's DevToolsActivePort sub-workflow is exemplary: it has a precise sequence (confirm Chrome → enable debugging → call list_pages → evaluate result) with a clear feedback loop (if still fails, proceed to advanced steps). Each step builds logically on the previous one.	3 / 3
Progressive Disclosure	The content is well-structured with clear headers and sub-sections, but it's a fairly long monolithic document (~100+ lines) with no references to supporting bundle files. The troubleshooting.md URL reference is good, but detailed error patterns and configuration examples could potentially be split into separate reference files for better organization.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ChromeDevTools/chrome-devtools-mcp
Commit: 2e039c0

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.