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.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/foundation-test-migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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 executable code and concrete commands, organized into a sensible migration sequence. Its main weaknesses are loose validation-checkpoint integration within the workflow and an all-inline structure that forgoes progressive disclosure into reference files.

Suggestions

Weave an explicit validate→fix→retry feedback loop into the migration steps (e.g., after BUILD.gn changes, run the Node and Browser commands, and on failure route to the relevant Pitfall before re-running) rather than leaving verification as a trailing section.

Split the Pitfalls & Troubleshooting and BUILD.gn Changes sections into separate reference files (e.g., PITFALLS.md, BUILD.md) and keep SKILL.md a leaner overview that links to them one level deep.

Tighten the intro and Core Concepts framing by removing rationale that restates what the migration steps already demonstrate (e.g., the "lighter, avoids global singletons... Isomorphic" clause).

DimensionReasoningScore

Conciseness

The body is mostly lean and actionable with little generic padding, but the intro rationale ("lighter, avoids global singletons... Isomorphic") and parts of the Core Concepts framing restate context that could be tightened, so it does not reach the every-token-earns-its-place bar of score 3.

2 / 3

Actionability

It provides fully executable, copy-paste-ready TypeScript (imports, describe blocks, sinon stubs, MockCDPConnection), concrete verification commands, and complete BUILD.gn snippets, matching the score-3 anchor.

3 / 3

Workflow Clarity

There is a clear numbered sequence (replace helpers, access via Universe, handle legacy singletons, BUILD.gn, verification) and explicit run commands, but validation is presented as a final section rather than explicit validate→fix→retry checkpoints woven into the steps, leaving the feedback loop implicit.

2 / 3

Progressive Disclosure

The single SKILL.md is well-sectioned with no nested references, but it is a comprehensive inline guide rather than an overview pointing to detailed materials; the Pitfalls, BUILD.gn, and legacy-singleton deep-dives are content that could be split into separate reference files, matching the score-2 anchor.

2 / 3

Total

9

/

12

Passed

Description

75%

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, distinctive, and cleanly pairs a concrete action with an explicit "Use when" trigger. It is slightly constrained by naming only one primary action and leaning on technical jargon rather than broad natural-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and a concrete action ("Migrating unit tests to foundation unit tests") plus the tools (TestUniverse, devtools_foundation_module), but it states a single action rather than listing multiple specific concrete actions, so it does not reach the score-3 anchor.

2 / 3

Completeness

It 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..."), with an explicit trigger clause matching the score-3 anchor.

3 / 3

Trigger Term Quality

It includes relevant, natural-for-the-niche triggers like "describeWithEnvironment", "describeWithMockConnection", and "DOM-heavy helpers", but these lean technical and lack common variations of a single concept, matching the score-2 anchor more than the broad coverage of score 3.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific to DevTools foundation test migration with named internal helpers, giving it distinct triggers unlikely to conflict with other skills, matching the score-3 anchor.

3 / 3

Total

10

/

12

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.