coverage

Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./engineering-team/playwright-pro/skills/coverage/SKILL.md

Quality

Content

68%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 well-structured, mostly lean instructional workflow with concrete per-step guidance and useful output templates. The main gap is the optional batch auto-generation step, which proposes generating tests for many gaps without a verification checkpoint, capping workflow clarity.

Suggestions

Add a verification checkpoint after Step 6's auto-generation (e.g., 'run the generated specs and report any failures before considering the gap closed') to lift workflow_clarity above the batch cap.

Tighten high-level steps like 'Identify critical paths' / 'Map multi-step workflows' into concrete signals (e.g., 'flag any route appearing in auth, checkout, or onboarding flows') to push actionability toward 5.

Clarify that templates/ and /pw:generate are provided by the parent plugin, or inline a minimal template pointer, so the skill's references are navigable without the surrounding bundle.

Dimension	Reasoning	Score
Conciseness	The body is efficient—bullet lists, a matrix template, and a prioritized plan with no padding explaining what coverage or tests are—matching the 'efficient, minor over-explanation' anchor; a couple of illustrative blocks could be trimmed, so not 5.	4 / 5
Actionability	Concrete, specific guidance throughout ('Scan route definitions (Next.js app/, React Router config, Vue Router)', 'Extract which pages/routes are covered (by page.goto() calls)') with usable output templates; a few steps like 'Identify critical paths' stay high-level, keeping it just below fully executable.	4 / 5
Workflow Clarity	Steps 1-6 are clearly numbered and sequenced, but the optional Step 6 invokes /pw:generate across multiple gaps (a batch operation) with no verify step (e.g., run the generated tests), so the batch-without-validation cap holds it at 3 rather than 4.	3 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with a single inline overview and one-level references to templates/; minor gap because the referenced templates/ and /pw:generate live outside this skill bundle (no references/ dir present), so navigation is not fully self-contained.	4 / 5
	Total	15 / 20 Passed

Description

86%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 description: it clearly states what the skill does and when to invoke it using six natural trigger phrases in third-person voice. The only weakness is that the 'what' lists a single action ('Analyze'), keeping specificity just above the midpoint rather than comprehensive.

Suggestions

Add 1-2 more concrete actions to the 'what' clause (e.g., 'Map testable surfaces, generate a coverage matrix, and prioritize gaps') to lift specificity from 3 toward 4-5.

Optionally note the output artifact (e.g., 'produces a prioritized coverage matrix') to further sharpen distinctiveness from generic testing skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('test coverage gaps') and one concrete action ('Analyze'), matching the 'names domain and 1-2 concrete actions' anchor; it is not 4 because only a single action is given rather than several specific ones.	3 / 5
Completeness	Explicitly answers both what ('Analyze test coverage gaps') and when ('Use when user says...') with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Six natural trigger phrases ('test coverage', 'what's not tested', 'coverage gaps', 'missing tests', 'coverage report', 'what needs testing') with synonym coverage, matching the comprehensive-natural-terms anchor.	5 / 5
Distinctiveness Conflict Risk	'Test coverage gaps' is a fairly distinct niche with specific triggers, but it overlaps with general testing/test-writing skills, so it is mostly distinct with minor overlap rather than fully clear-cut.	4 / 5
	Total	17 / 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: alirezarezvani/claude-skills
Path: engineering-team/playwright-pro/skills/coverage/SKILL.md
Commit: 19392f7

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