chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).
90
87%
Does it follow best practices?
Impact
94%
1.59xAverage score across 3 eval scenarios
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 solid skill description that clearly communicates its purpose and when to use it. It has good trigger term coverage and explicit 'Use when' guidance with a helpful exclusion clause. The main area for improvement is adding more specific concrete actions beyond the high-level categories of debugging, automation, and analysis.
Suggestions
Add more granular concrete actions such as 'set breakpoints, capture screenshots, inspect DOM elements, monitor console logs, profile page load times' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Chrome DevTools, browser automation, debugging) and mentions several action areas (debugging, troubleshooting, performance analysis, network inspection), but doesn't list multiple concrete granular actions like 'set breakpoints, capture screenshots, modify DOM elements'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Chrome DevTools via MCP for debugging, troubleshooting, browser automation) and 'when' with an explicit 'Use when...' clause listing four trigger scenarios. Also includes a helpful exclusion note about slim mode. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'debugging web pages', 'browser automation', 'performance', 'network requests', 'Chrome DevTools', 'browser interactions'. These cover the main ways users would phrase requests in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Chrome DevTools via MCP, which is a distinct niche. The mention of MCP, Chrome DevTools, and specific use cases like network inspection and performance analysis make it unlikely to conflict with general web development or testing skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently communicates Chrome DevTools MCP usage patterns. Its strengths are excellent workflow clarity with proper sequencing and good progressive disclosure. The main weakness is that actionability could be improved with concrete executable examples (e.g., actual tool call syntax or JSON payloads) rather than just naming tools and parameters.
Suggestions
Add a concrete, copy-paste ready example of a full tool call sequence (e.g., showing the actual MCP tool invocation syntax for navigate → snapshot → click) to improve actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what Chrome DevTools, MCP, accessibility trees, and UIDs are. No unnecessary explanations of basic concepts; every section delivers actionable information without padding. | 3 / 3 |
Actionability | The skill provides clear tool names and parameter references (e.g., `filePath`, `pageIdx`, `includeSnapshot: false`) and describes workflows with specific tool sequences, but lacks executable code examples or copy-paste ready commands. The guidance is concrete but stops short of fully executable snippets. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (navigate → wait → snapshot → interact) with explicit ordering constraints. The extension testing workflow has 5 clear steps with verification checkpoints (verify service worker, verify page behavior). The troubleshooting section provides fallback paths. | 3 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Core Concepts, Workflow Patterns, Troubleshooting) with clear headers and subsections. External references are one level deep and clearly signaled (Chrome DevTools docs, troubleshooting guide). For a skill with no bundle files, the structure is appropriately self-contained. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
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.