browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The body is highly actionable with clear, validated workflows and concrete examples, but it is a long monolithic file with some redundancy across the security/rationalizations/red-flags sections and no progressive disclosure via reference files.

Suggestions

Consolidate the overlapping untrusted-data guidance currently spread across Security Boundaries, Common Rationalizations, and Red Flags into a single section to reduce repetition and token cost.

Move the detailed workflow templates, console analysis patterns, and accessibility verification into separate reference files (e.g. WORKFLOWS.md, ACCESSIBILITY.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Trim the body to a leaner overview so SKILL.md stays a pointer to the deeper material rather than embedding all of it inline.

Dimension	Reasoning	Score
Conciseness	Content is skill-specific and mostly efficient, but the untrusted-data theme is restated across Security Boundaries, Common Rationalizations, and Red Flags, and the ~315-line body could be tightened by consolidating that overlap.	2 / 3
Actionability	Provides copy-paste-ready .mcp.json config, a concrete tools table, and a detailed test-plan template with exact URLs and expected requests like "PATCH /api/tasks/:id with { status: \"completed\" }", giving fully executable guidance.	3 / 3
Workflow Clarity	Three workflows (UI bugs, network, performance) are clearly sequenced with explicit validation checkpoints — VERIFY/MEASURE steps, baseline comparisons, and a checkbox verification checklist — including feedback loops.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a single ~315-line monolithic file with no bundle references; material like the detailed workflow templates and console/a11y patterns could be split into one-level-deep reference files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 specific, trigger-rich, and clearly answers both what it does and when to use it in third-person voice, with a distinct MCP-gated niche. It is a strong, concise description with no notable weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output" — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Clearly states what ("Tests in real browsers via Chrome DevTools MCP" plus capabilities) and when via two explicit "Use when..." trigger clauses, satisfying both what and when.	3 / 3
Trigger Term Quality	Covers natural user phrasing such as "building or debugging anything that runs in a browser", "inspect the DOM", "capture console errors", and "profile performance", which users would naturally say.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Chrome DevTools MCP browser testing) and is gated by "Requires the chrome-devtools MCP server to be configured", making conflict with other skills unlikely.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: addyosmani/agent-skills
Commit: 70b7506

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.