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.52x

Quality

81%

Does it follow best practices?

Impact

90%

1.52x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%Weight 40%Scale 1-5

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

The body is a highly actionable, well-sequenced diagnostic workflow with concrete commands, flags, and validation feedback loops. Its main weakness is mild verbosity in a few explanatory sentences that assume less competence than necessary.

Suggestions

Trim meta-commentary such as 'Your primary goal is to guide the user...' and 'This is the simplest and safest way to verify...' to tighten the conciseness score.

Consider moving the detailed error-symptom catalog (Steps 2-3) into a separate references file linked from a concise overview, which would improve progressive_disclosure.

Replace the explanatory 'This is not a generic connection failure' framing with a direct instruction to reduce over-explanation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and practical, but includes mild meta-commentary and over-explanation ('Your primary goal is to guide the user...', 'This is the simplest and safest way...') that could be trimmed; not a 4 because several sentences pad rather than instruct.	3 / 5
Actionability	Provides fully executable, copy-paste-ready guidance: specific config files to search, exact commands ('npx chrome-devtools-mcp@latest --help', the 'gh issue list ... --search' invocation), concrete flags ('--browser-url=http://127.0.0.1:9222', '--logFile', 'startup_timeout_ms' 20000), and specific URLs covering the common cases.	5 / 5
Workflow Clarity	Six clearly sequenced steps with explicit validation checkpoints and feedback loops ('If list_pages succeeds, the problem is resolved. If it still fails ... then you can proceed to the more advanced steps'); this is a diagnostic (non-destructive) workflow, so the batch/destructive cap does not apply.	5 / 5
Progressive Disclosure	Well-organized into six clearly headed step sections with one clearly signaled external reference (the GitHub troubleshooting.md URL); not a 5 because the skill exceeds ~50 lines and the inline error catalog could arguably be split into a reference file, leaving a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

82%Weight 40%Scale 1-5

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

The description is well-structured, explicitly answering both 'what' and 'when' with concrete, domain-specific trigger terms and low conflict risk. Its only weakness is that the capability statement ('troubleshoot') is somewhat generic rather than enumerating specific actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Chrome DevTools MCP') and 1-2 concrete actions ('troubleshoot connection and target issues'), but 'troubleshoot' is generic and no further specific capabilities are enumerated; not a 4 because it does not list several specific actions.	3 / 5
Completeness	Clearly states both what ('Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues') and when ('Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Concrete trigger keywords a user would actually hit ('list_pages, new_page, or navigate_page fail', 'server initialization fails') give good coverage; not a 5 because synonyms and additional natural variations are absent.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to Chrome DevTools MCP troubleshooting with named tools, giving it a clear niche and minimal overlap risk with unrelated skills.	5 / 5
	Total	17 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ChromeDevTools/chrome-devtools-mcp
Path: skills/troubleshooting/SKILL.md
Commit: fce756a

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.