CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 thorough, highly actionable migration skill with executable code throughout and clear verification guidance. It is well-structured and self-contained, with only minor room for tightening prose and embedding validation inline.

Suggestions

Tighten the Core Concepts bullets and a few explanatory sentences (e.g. the TestUniverse Lazy/Scoped/Explicit lines) to reduce remaining verbosity.

Move the Node/Browser verification commands into a per-step checkpoint within the migration flow rather than isolating them in a trailing section, so validation is interleaved with the steps.

DimensionReasoningScore

Conciseness

The body is largely lean and skill-specific (Core Concepts bullets, code-focused migration steps) with no generic-concept padding, though a few explanatory sentences could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready TypeScript imports, sinon stubs, MockCDPConnection usage, BUILD.gn snippets, and exact npm test commands covering the common migration cases.

5 / 5

Workflow Clarity

A clear numbered migration sequence plus an explicit Verification section (Node and Browser runtimes) and a Pitfalls troubleshooting block; validation lives in a separate section rather than as per-step checkpoints.

4 / 5

Progressive Disclosure

Well-organized into focused sections (Core Concepts, Migration Guide, Pitfalls, BUILD.gn, Verification) with no external references needed; good structure with only minor organization gaps.

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 the task and provides explicit 'Use when' trigger guidance with concrete API names. It is well-distinguished from generic skills and avoids vague fluff.

DimensionReasoningScore

Specificity

Names concrete tools (TestUniverse, devtools_foundation_module) and the migration action away from specific legacy helpers (describeWithEnvironment, describeWithMockConnection), with only minor coverage gaps.

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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when moving tests away from DOM-heavy helpers like describeWithEnvironment or describeWithMockConnection' clause supplies natural trigger terms users would cite, though a few common variations are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow niche with named DevTools APIs, giving it distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ChromeDevTools/devtools-frontend
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.