CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/lcov-analysis

Use for any question or task about LCOV .info or Cobertura XML coverage files, including reading one or finding which files fail a line gate. Parses per-file line, function and branch metrics from gcov, llvm-cov, coverage.py, JaCoCo, Jest, nyc or coverlet output, compares with a baseline and returns per-file pass or fail verdicts for a cross-language gate.

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

86%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-engineered skill body: executable parser code with a subtle-correctness note (distrusting summary fields), a genuinely instructive anti-patterns table capturing team-learned pitfalls, and clean delegation of bulk detail to two well-labeled reference files. The only real weakness is mild over-explanation in the Overview of LCOV toolchain basics Claude already knows.

DimensionReasoningScore

Conciseness

The body is largely lean — a worked .info record, executable parser, gate rules with concrete thresholds, and a high-value anti-patterns table — but the Overview explains the LCOV toolchain (geninfo/lcov/genhtml roles, 'lingua franca') that Claude already knows and could be trimmed. Not 3 since no section is padded; not 5 since the Overview over-explains.

4 / 5

Actionability

The parse_lcov.py code is complete and executable (handles checksum-extended DA lines and '-' BRDA taken counts), the worked example shows exactly how to read a record, and the gate rules give concrete default thresholds (N=0.5pp, M=5pp, 80% line / 70% branch) — copy-paste ready guidance covering the common case.

5 / 5

Workflow Clarity

'How to use' gives a clear 4-step sequence (confirm CI output → parse/recompute → cache baseline/diff → gate) with a real correctness checkpoint ('recompute totals from the per-line records rather than trusting the summary fields'). Not 3 since validation guidance exists and the operation is non-destructive reporting; not 5 since there is no explicit error-recovery loop (e.g., what to do on malformed or partial records).

4 / 5

Progressive Disclosure

The body keeps the overview and core parse inline while clearly signaling one-level-deep references (format-diff-and-ci.md for the keyword table, diff+gate implementation and CI wiring; cobertura.md for the sibling format) — both real files that link only externally and back to SKILL.md, with each reference annotated by content. Navigation is easy and the split is appropriate.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: third-person voice, explicit 'Use for...' trigger clause, concrete multi-action capability statement, and a comprehensive set of natural trigger terms spanning formats, extensions, and tool names. It is dense rather than padded — every clause adds capability or trigger information.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Parses per-file line, function and branch metrics", "compares with a baseline", "returns per-file pass or fail verdicts", "finding which files fail a line gate" — with comprehensive coverage across seven named coverage tools, matching the top anchor rather than the 'minor gaps' level 4.

5 / 5

Completeness

It explicitly answers both: what ("Parses per-file line, function and branch metrics... compares with a baseline and returns per-file pass or fail verdicts") and when ("Use for any question or task about LCOV .info or Cobertura XML coverage files, including reading one or finding which files fail a line gate") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers include "LCOV .info", "Cobertura XML", "coverage files", "line gate" plus tool names users actually say (gcov, llvm-cov, coverage.py, JaCoCo, Jest, nyc, coverlet) and file extensions, providing comprehensive synonym and extension coverage as in the level-5 anchor.

5 / 5

Distinctiveness Conflict Risk

The niche — parsing LCOV/Cobertura coverage files for per-file PR gating — is clear and specific, with named tools and formats making it unlikely to trigger for the wrong skill; no overlap risk beyond closely adjacent coverage skills, which the tool list disambiguates.

5 / 5

Total

20

/

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: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page