install-chrome-devtools-mcp

Install Chrome DevTools MCP server for debugging and network inspection in Claude Code

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/product-design/skills/install-chrome-devtools-mcp/SKILL.md

Quality

Discovery

40%

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 identifies a specific tool (Chrome DevTools MCP server) with a clear niche, but suffers from incomplete guidance. It lacks explicit trigger conditions ('Use when...') and could benefit from more specific action verbs and natural user keywords like 'browser debugging' or 'inspect network requests'.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user wants to debug web pages, inspect network requests, or set up browser developer tools integration'

Expand trigger terms to include natural variations users would say: 'browser debugging', 'dev tools', 'inspect element', 'network traffic', 'console logs'

List more specific concrete actions: 'inspect DOM elements, capture network requests, debug JavaScript, analyze page performance'

Dimension	Reasoning	Score
Specificity	Names the domain (Chrome DevTools MCP server) and mentions two actions (debugging, network inspection), but doesn't list comprehensive concrete actions like 'inspect DOM elements, capture network requests, analyze performance metrics'.	2 / 3
Completeness	Describes what it does (install Chrome DevTools MCP server) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Chrome DevTools', 'MCP server', 'debugging', 'network inspection', and 'Claude Code', but misses common variations users might say like 'browser debugging', 'dev tools', 'inspect element', 'network traffic', or 'console'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Chrome DevTools MCP server' and 'Claude Code' creates a clear, specific niche that is unlikely to conflict with other skills - it's distinctly about browser debugging integration.	3 / 3
	Total	8 / 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 solid, actionable skill with excellent executable examples and clear installation commands. The main weakness is verbosity - content is duplicated between sections (browser modes appear twice), and the document could be more concise by moving detailed troubleshooting and advanced configurations to separate files. The comparison table with Playwright and comprehensive tool listing add value.

Suggestions

Remove duplicate browser connection mode explanations - consolidate into a single section

Move the 'What This Does' bullet list to after the installation command or remove it entirely since the Available Tools section covers this more thoroughly

Consider moving Troubleshooting and Browser Connection Modes to separate reference files, keeping only the basic installation in SKILL.md

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some redundancy - browser connection modes are explained twice (once in Common Configurations and again in Browser Connection Modes section), and the 'What This Does' section explains capabilities Claude could infer from the tool list.	2 / 3
Actionability	Excellent executable commands throughout with copy-paste ready bash commands for every configuration option, platform-specific instructions, and clear verification steps.	3 / 3
Workflow Clarity	Clear installation workflow with explicit verification steps (restart, run /mcp, test command). Troubleshooting section provides good error recovery guidance with specific diagnostic steps.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the document is quite long (~200 lines) and could benefit from splitting detailed troubleshooting and browser connection modes into separate reference files.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

Reviewed: 29 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.