CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/coverage-py-analysis

Use for any question or task about Python code coverage with pytest or unittest, including quick how-to questions, a CI gate on a minimum, and coverage that drops when tests run in parallel with xdist: coverage run, branch coverage, combining parallel data, .coveragerc source, omit and fail_under, and terminal, HTML, Cobertura XML, LCOV or JSON reports for CI.

Quality

84%

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

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

Highly actionable content with complete, executable code and a clear step sequence. Its weaknesses are token efficiency (background Claude already knows, repeated attributions, dated version info) and a monolithic structure that inlines a script and CI config a bundle could carry separately.

Suggestions

Trim concepts Claude already knows — the quoted 'Coverage.py is a tool for measuring code coverage...' overview and the explanation of what branch coverage catches — and move the version/date snapshot ('7.13.5, March 2026, fetched 2026-05-05') into a clearly labeled version/deprecated section or drop it.

Move the per-file gate script into a real scripts/per_file_gate.py bundle file (the CI YAML already references that path, but no scripts/ directory exists) and consider moving the full GitHub Actions workflow to a references/ file, keeping SKILL.md as an overview.

Add an explicit error-recovery loop for the coverage gates (what to inspect and retry when fail_under or the per-file gate fails, e.g., 'run coverage report --show-missing for the failing path, add or omit tests, re-run') to reach a full validation workflow.

DimensionReasoningScore

Conciseness

Mostly efficient but includes unnecessary material: a quoted definition of what Coverage.py is, an explanation of what branch coverage catches (both concepts Claude already knows), seven repeated 'Per [coveragepy-docs][cov]' attribution prefixes, and time-sensitive version info ('As of the source fetch on 2026-05-05, Current version is 7.13.5 (March 2026)') that sits outside any old-patterns/deprecated section. These are more than the 'minor instances' of anchor 4.

3 / 5

Actionability

Fully executable throughout: a complete canonical .coveragerc, copy-paste command chains ('coverage run --parallel -m pytest -n auto; coverage combine ...'), a complete runnable per_file_gate.py script, and a full GitHub Actions workflow YAML. Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Steps 1-8 are clearly sequenced (install → branch → config → combine → format → gate → pragma → CI) with explicit enforcement checkpoints (fail_under exit-code behavior, per-file gate with sys.exit(1)). It falls short of anchor 5 because there are no error-recovery feedback loops (e.g., what to do when the gate fails) — checkpoints exist but retry guidance is absent.

4 / 5

Progressive Disclosure

Section structure is good, but this is a ~315-line monolith: the full per-file gate script, the CI YAML, and the complete config are all inlined rather than split into scripts/ or references/ files. The CI YAML references 'scripts/per_file_gate.py' yet no scripts/ directory exists in the bundle, so content that should be separate is inline — anchor 3.

3 / 5

Total

15

/

20

Passed

Description

92%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: concrete capability list, explicit and scenario-rich trigger guidance, and tool-specific terminology that keeps it distinct. The only gap is minor — missing the tool name 'coverage.py' and the 'test coverage' synonym in the trigger vocabulary.

DimensionReasoningScore

Specificity

Lists many concrete capabilities with config-level detail: 'coverage run, branch coverage, combining parallel data, .coveragerc source, omit and fail_under, and terminal, HTML, Cobertura XML, LCOV or JSON reports'. This matches the anchor for multiple specific concrete actions with comprehensive coverage; anchor 4's 'minor gaps' understates the breadth.

5 / 5

Completeness

Explicitly answers both: the trigger clause 'Use for any question or task about Python code coverage with pytest or unittest, including quick how-to questions, a CI gate on a minimum, and coverage that drops when tests run in parallel with xdist' gives concrete 'when' scenarios, and the colon-separated capability list gives 'what'. Matches the anchor for explicit what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keywords users would say: 'Python code coverage', 'pytest', 'unittest', 'CI gate', 'xdist', 'branch coverage', 'LCOV'. However the tool name 'coverage.py' itself never appears and the common synonym 'test coverage' is missing, so it falls short of anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

Scoped to Python coverage with pytest/unittest and tool-specific terms (xdist, .coveragerc, fail_under, Cobertura, LCOV), giving a clear niche with distinct triggers and minimal conflict risk with adjacent JS/Java coverage skills.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page