CtrlK
BlogDocsLog inGet started
Tessl Logo

fixing-skipped-tests

Use this skill when unskipping a test that was previously skipped.

56

Quality

63%

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/fixing-skipped-tests/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a lean, well-structured workflow with concrete commands, explicit validation checkpoints, and feedback loops for a batch operation, appropriately scoped for a short instruction-only skill.

DimensionReasoningScore

Conciseness

The ~28-line body is lean and mostly assumes Claude's competence, with concrete commands earning their place; only minor trims (e.g. restating the --repeat flag behavior for both E2E and unit) keep it just below the fully-lean score 5 anchor.

4 / 5

Actionability

It gives concrete, executable guidance — exact test IDs (`npm run test path/to/foo.test.ts:test_name`), `--repeat=20`, the `test/TestExpectations` path, and `fixed-<bugid>` branch naming — but defers branch-creation and verification specifics to other skills, a minor gap versus the copy-paste-ready score 5.

4 / 5

Workflow Clarity

The five-step sequence is clearly ordered with explicit validation checkpoints (re-run the test, re-run after fixing, verify full build) and a feedback loop (run → analyze failure → fix → re-run); because validation is present the batch-operation cap at 3 does not apply, but the vague 'as required by the repository best practices' final step keeps it below the checklist-level score 5.

4 / 5

Progressive Disclosure

With no bundle files and well-organized section headers under 50 lines, this meets the simple-skill exception where progressive disclosure scores 5 on well-organized sections alone; the inline references to sibling skills are one-level and clearly signaled.

5 / 5

Total

17

/

20

Passed

Description

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

The description provides a clear explicit trigger for a well-defined niche, but it essentially restates the skill name without describing concrete actions, leaving the 'what' weak and tautological with the 'when'.

Suggestions

Add a brief 'what' clause naming concrete actions, e.g. 'Remove [ Skip ] expectations from test/TestExpectations, re-run the targeted tests, and clean up skip markers in code.'

Broaden trigger terms with natural synonyms users might say, such as 're-enable', 'fix skipped', or 'flaky test'.

Mention the DevTools/TestExpectations context so the trigger is more distinctive from generic test-fixing skills.

DimensionReasoningScore

Specificity

The phrase 'unskipping a test that was previously skipped' names a specific domain but lists no concrete actions beyond restating the trigger, matching the 'names the domain but actions are minimal or generic' anchor rather than the vague-no-domain score 1 or the multi-action score 3.

2 / 5

Completeness

An explicit 'Use this skill when...' trigger is present (so not capped for a missing trigger clause), but the 'what' is tautological with the 'when' — it never describes what the skill actually does (extract bug ID, edit TestExpectations, re-run tests), leaving the what weakly answered rather than the clear-both anchor at 4.

3 / 5

Trigger Term Quality

It includes relevant keywords ('unskipping a test', 'skipped') with an explicit 'Use this skill when' trigger, but misses common synonyms and variations a user might say ('re-enable test', 'fix skipped test', 'flaky test'), fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Unskipping a previously skipped test' is a clear, narrow niche unlikely to fire for unrelated skills, but it could overlap with general test-fixing or flakiness skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict score 5.

4 / 5

Total

12

/

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.