foundation-test-migration

Migrating unit tests to foundation unit tests using TestUniverse and devtools_foundation_module. Use when moving tests away from DOM-heavy helpers like describeWithEnvironment or describeWithMockConnection.

Quality

85%

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

82%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 highly actionable, well-structured migration guide with executable examples and verification steps. The main gap is an explicit validation feedback loop tying the verification commands back into the migration workflow.

Suggestions

Add an explicit feedback loop after the Verification section: if Node or Browser tests fail, return to the relevant migration step (e.g. singleton init order or DOM globals) and re-run, which would lift workflow_clarity to 5.

Tighten the intro paragraph and the TestUniverse 'Lazy/Scoped/Explicit' bullets to assume Claude's competence, trimming tokens that restate context already implied by the code.

Consider moving the detailed Pitfalls & Troubleshooting cases into a references file linked from the body, leaving the core migration steps leaner in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code and minimal padding; a few explanatory sentences (e.g. the intro paragraph and the TestUniverse 'Lazy/Scoped/Explicit' bullets) restate context Claude could infer, keeping it just below the lean 5 anchor.	4 / 5
Actionability	Provides copy-paste-ready TypeScript, sinon stubs, MockCDPConnection usage, BUILD.gn snippets, and concrete verification commands covering the common migration cases.	5 / 5
Workflow Clarity	Clear multi-step sequence (replace helpers, access dependencies, handle legacy singletons, BUILD.gn, verify) with a verification section; lacks an explicit run-fail-fix rerun loop, though the Pitfalls section supplies error-recovery guidance, so it sits below the 5 anchor.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and no nested references; with no bundle files present and most content appropriately inline, it is well-structured but slightly above the size where a few sections (detailed pitfalls, BUILD.gn examples) could plausibly be split out.	4 / 5
	Total	17 / 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 strong, specific description that clearly states what the skill does and when to use it, with concrete domain-specific trigger terms. Minor additional action/synonym coverage could push specificity and trigger_term_quality to the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('Migrating unit tests to foundation unit tests') and several concrete tools ('TestUniverse', 'devtools_foundation_module'); not a comprehensive list of distinct actions but more than 1-2, so just below the 5 anchor.	4 / 5
Completeness	Explicitly answers both what ('Migrating unit tests to foundation unit tests using TestUniverse and devtools_foundation_module') and when ('Use when moving tests away from DOM-heavy helpers like...') with concrete trigger phrases, and uses third person voice.	5 / 5
Trigger Term Quality	Includes natural domain triggers like 'moving tests away from DOM-heavy helpers' plus specific helper names ('describeWithEnvironment', 'describeWithMockConnection'); a few common variations are missing, so it sits between the 3 and 5 anchors, closer to 4.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (foundation test migration) with distinct, project-specific triggers (TestUniverse, describeWithEnvironment, describeWithMockConnection); minimal overlap risk with other 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/foundation-test-migration/SKILL.md
Commit: 31f2967

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