devtools-testing-guidance

Guidance on selecting the appropriate test suite (Unit, API, or E2E tests) when writing new tests in Chrome DevTools. MUST be used when writing new tests.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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.

A tight, actionable, well-structured selection guide that stays in scope and points elsewhere for adjacent concerns. It assumes Claude's competence and gives concrete file paths and build targets, with no notable weaknesses.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized with no padding or explanation of concepts Claude already knows; every section earns its place and assumes competence.	5 / 5
Actionability	Provides concrete, executable guidance: specific file extensions ('.test.ts', '.test.api.ts'), directory locations, named helpers ('TestUniverse'), and exact BUILD.gn target names for each suite type.	5 / 5
Workflow Clarity	Single-purpose selection skill with a clear decision structure (Unit as default, API and E2E with explicit 'when to use' triggers); per the simple-skill exception, a clear unambiguous single action scores 5, and no destructive/batch cap applies.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and a clearly signaled pointer to the sibling devtools-verification skill for out-of-scope how-to-run details; no nested references.	5 / 5
	Total	20 / 20 Passed

Description

87%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.

A concise, third-person description that clearly states its purpose and includes an explicit usage trigger, with good natural keyword coverage and a distinct niche. Minor room for broader synonym coverage and listing more concrete actions.

Suggestions

Add natural synonyms like 'add a test' or 'increase test coverage' to broaden trigger-term coverage.

Consider listing one or two concrete actions (e.g. 'add the test file and update its BUILD.gn target') to push specificity toward a 5.

Dimension	Reasoning	Score
Specificity	Names the domain ('selecting the appropriate test suite') and enumerates concrete options ('Unit, API, or E2E tests') for Chrome DevTools; it is one core action rather than multiple distinct actions, so just below a 5.	4 / 5
Completeness	Explicitly states both what it does ('Guidance on selecting the appropriate test suite') and when to use it ('MUST be used when writing new tests'), matching the explicit-trigger anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('writing new tests', 'test suite', 'Unit, API, or E2E tests', 'Chrome DevTools') but misses common synonyms like 'add a test' or 'test coverage'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (DevTools test-suite selection across three named suite types) with distinct triggers and minimal overlap with sibling skills.	5 / 5
	Total	18 / 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/devtools-frontend
Path: .agents/skills/devtools-testing-guidance/SKILL.md
Commit: 31f2967

Reviewed: ~16 hours 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.