CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/jest-coverage-analysis

Configures Jest's built-in coverage (Istanbul-instrumented `babel` provider or V8-native `v8` provider), wires the right `coverageReporters` for downstream consumption (`lcov` for SaaS / cross-tool, `cobertura` for Jenkins, `text-summary` for terminal, `html` for human review), authors per-file `coverageThreshold` rules that focus the gate on critical paths (vs the global-only foot-gun), and parses the per-file JSON output for PR-time deltas. Use when the project tests with Jest (or Vitest, which uses the same Istanbul/V8 provider) and the team needs PR-time coverage signal that's both local-runnable and CI-gateable.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable Jest/Vitest coverage skill with explicit validation feedback loops and a properly used one-level reference file. Its only weakness is mild verbosity from verbatim documentation quotes and a conceptual comparison table that assume less than Claude knows.

Suggestions

Replace the verbatim Jest-doc quotes in the Overview and Step 1 with a one-line paraphrase plus the doc link; Claude can fetch the exact wording if needed.

Condense the Step 1 provider pros/cons table to the single decision-relevant fact per provider (babel = mature ignore comments; v8 = faster but source-map edge cases), or move it into the references file.

Trim the Limitations section to the actionable guidance (e.g. 'switch to `babel` under multi-transform source maps') and drop the conceptual framing of why coverage ≠ correctness.

DimensionReasoningScore

Conciseness

The body is largely actionable config rather than concept padding, but verbatim Jest-doc quotes (e.g. "Indicates which provider should be used to instrument code for coverage") and a conceptual provider pros/cons table are content Claude largely knows and could be tightened, fitting the 'mostly efficient but could be tightened' anchor rather than the lean 3.

2 / 3

Actionability

Provides fully executable, copy-paste-ready blocks: Jest/Vitest config objects, a Node JSON parser, and a CI YAML with `npx jest --coverage` and `codecov/codecov-action@v4`, matching the executable-code anchor.

3 / 3

Workflow Clarity

Steps 1–7 are clearly sequenced and Step 3 includes an explicit validation checkpoint with a feedback loop ("Verify the gate fires... If it exits 0, check that `collectCoverageFrom`... then re-run"), satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The SKILL.md is an overview that offloads the full parser and anti-pattern catalog to a real one-level-deep reference ([references/parsing-and-anti-patterns.md](references/parsing-and-anti-patterns.md)), with clearly signaled, well-organized navigation rather than nested or monolithic content.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that names concrete configuration actions, supplies an explicit 'Use when' trigger covering Jest and Vitest, and occupies a distinct niche. No first/second-person voice or vague fluff to penalize.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Configures Jest's built-in coverage", "wires the right `coverageReporters`", "authors per-file `coverageThreshold` rules", and "parses the per-file JSON output for PR-time deltas" — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly answers both what and when via the clause "Use when the project tests with Jest (or Vitest...) and the team needs PR-time coverage signal that's both local-runnable and CI-gateable", clearing the bar that caps completeness at 2 when 'Use when' is missing.

3 / 3

Trigger Term Quality

Natural user-facing terms recur throughout ("Jest", "Vitest", "coverage", "PR-time coverage signal", "CI-gateable") alongside the technical config detail, giving good coverage of what a user would actually say; not merely jargon-only like the 1 anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Jest/Vitest coverage gating, a clear niche with distinct triggers unlikely to fire for unrelated skills; not generic like the 1 anchor ("Helps with code and documents").

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents