CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-coverage

Use when reviewing CI coverage, automated checks, or test strategy related to Maintain test coverage thresholds. Focus on whether the rule is continuously verified, not just documented.

Quality

78%

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 ./skills/test-coverage/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 well-structured, appropriately brief overview with concrete numbers and a clean task-mode layout, and it correctly pushes implementation detail into a verified one-level-deep reference file. The main improvement is disambiguating the overlapping 'Check' and 'Code Review' sections and trimming the conceptual opening sentence.

Suggestions

Disambiguate 'Check' vs 'Code Review' — e.g., state that Check is for a quick audit while Code Review is for flagging exact enforcement gaps in diffs/PRs.

Cut the opening explanatory sentence about what coverage thresholds do; Claude already knows this and the 'Quick Reference' carries the useful content.

Add a brief verification cue in the Fix section (e.g., confirm the CI job fails when coverage drops below threshold) to close the feedback loop.

DimensionReasoningScore

Conciseness

The body is lean overall, but the opening sentence 'Coverage thresholds prevent code quality from degrading over time by failing builds when test coverage drops below safe levels' explains a concept Claude already knows, and the 'Explain' section restates the skill's purpose. Minor over-explanation that could be trimmed matches the anchor at 4, short of the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Concrete, specific guidance throughout: exact threshold numbers ('70% branches, 80% lines/functions/statements'), named exclusions ('generated code, type definitions, and config files'), and named frameworks ('Jest, Vitest'). The executable code example lives one level deep in references/rule.md (verified present with a complete jest.config.js), so guidance is mostly executable with minor gaps — anchor 4 rather than 3, since the directions are specific rather than high-level hints.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure gives unambiguous per-mode instructions for a simple, non-destructive skill, so the simple-skill exception applies. However, 'Check' and 'Code Review' overlap without guidance on when to use which, and there is no explicit verification step (e.g., confirming CI actually blocks merges). Clear sequence with minor gaps matches anchor 4, not the explicit-validation anchor at 5.

4 / 5

Progressive Disclosure

The body is ~45 lines of well-organized overview sections, with a single clearly-signaled, one-level-deep reference ('see references/rule.md') that exists on disk and appropriately holds the full code examples and framework guidance. This matches the anchor for a clear overview with well-signaled one-level-deep references and appropriate content split.

5 / 5

Total

17

/

20

Passed

Description

70%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 has a solid explicit 'Use when...' trigger with natural keywords, but it is trigger-heavy and capability-light: it never states what the skill does. Adding one concrete capability statement (e.g., configuring coverageThreshold in Jest/Vitest and wiring CI checks) would raise both specificity and completeness.

Suggestions

Add a concrete 'what' statement, e.g., 'Configure coverage thresholds (branches, functions, lines, statements) in Jest or Vitest configs and enforce them as CI gates.'

Include natural trigger variations users actually say, such as 'code coverage', 'CI/CD pipeline', or 'coverageThreshold', to improve trigger term coverage.

Trim the generic phrase 'related to Maintain test coverage thresholds' — it reads as scaffolding and dilutes the trigger.

DimensionReasoningScore

Specificity

The description names the domain ('reviewing CI coverage, automated checks, or test strategy') and one or two actions ('Focus on whether the rule is continuously verified'), but 'related to Maintain test coverage thresholds' is generic and it lists no concrete capabilities like configuring threshold values or reviewing CI configs. This matches the anchor for domain plus 1-2 concrete actions without comprehensive coverage, falling short of the several-specific-actions anchor at 4.

3 / 5

Completeness

The 'when' is explicit ('Use when reviewing CI coverage, automated checks, or test strategy'), but the 'what' is only implied by the focus clause — the description never states what the skill actually does (e.g., configure thresholds in Jest/Vitest, review CI enforcement). This fits the anchor where both are present but one could be more explicit, rather than the clear-what-and-when anchor at 5 or the vague-what anchor at 3.

4 / 5

Trigger Term Quality

Terms like 'CI coverage', 'test coverage', 'automated checks', and 'test strategy' are natural phrases users would say. Common variations are missing — 'code coverage', 'CI/CD', 'coverage threshold', and framework names (Jest, Vitest) — which keeps it below the comprehensive-synonyms anchor at 5 but clearly above the missing-variations anchor at 3.

4 / 5

Distinctiveness Conflict Risk

'Test coverage thresholds' plus CI verification is a clear niche with distinct triggers, but it could overlap with adjacent testing/CI-checklist skills (e.g., running tests in CI, lint gates). Minor overlap risk with closely related skills matches the anchor at 4, not the minimal-conflict anchor at 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/test-coverage/SKILL.md

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.