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-crafted skill description with excellent trigger terms and completeness. It clearly defines 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

Expand the capability description to list specific troubleshooting actions, e.g., 'diagnoses connection failures, resolves stale target references, verifies server configuration' instead of the generic 'troubleshoot connection and target issues'.

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', 'connection and target issues'. These are exactly the terms a user or Claude would encounter when hitting these errors.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche — Chrome DevTools MCP troubleshooting with specific function names as triggers. Very unlikely to conflict with other skills.	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 escalation paths. The main weaknesses are minor verbosity (some preamble and repeated instructions) and the monolithic structure that could benefit from splitting detailed error patterns into separate referenced files.

Suggestions

Trim the introductory paragraph — Claude doesn't need to be told it's 'acting as a troubleshooting wizard'; jump straight into Step 1.

Consider extracting the detailed error patterns (Step 2 subsections) into a separate ERRORS.md reference file to improve progressive disclosure and reduce the main file length.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and provides specific, useful troubleshooting steps. However, there's some verbosity in explanations (e.g., the preamble about 'You are acting as a troubleshooting wizard') and some instructions that could be tightened, like the repeated reminders to ask for configuration.	2 / 3
Actionability	The skill provides highly concrete, actionable guidance: specific file paths to check, exact error messages to match, specific URLs to navigate to (chrome://inspect/#remote-debugging), exact CLI commands to run (npx, gh issue list), and specific flags to check. The troubleshooting steps are copy-paste ready and leave little ambiguity.	3 / 3
Workflow Clarity	The 6-step diagnostic process is clearly sequenced from simple (read config) to complex (search GitHub issues). The DevToolsActivePort error section has an explicit feedback loop: try fix → call list_pages → if success, done; if fail, escalate. Validation checkpoints are built into the workflow (e.g., 'Only then should you ask', 'your only next action should be to call list_pages').	3 / 3
Progressive Disclosure	The content is well-structured with clear headers and sub-sections, but it's a fairly long monolithic document with no references to supporting bundle files. The troubleshooting.md GitHub link serves as an external reference, but the detailed error patterns and configuration guidance could benefit from being split into separate referenced files for different error categories.	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: faac61d

Reviewed: 3 days 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.