CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cobertura-analysis

Parses Cobertura XML coverage reports (the JVM-canonical format originally from the cobertura-cobertura tool, also emitted by JaCoCo `--coverage-xml`, coverage.py `--xml`, Istanbul / Jest `cobertura` reporter, gocover-cobertura, and dotnet's `coverlet`). Walks the coverage-04 DTD structure (coverage → packages → classes → methods → lines + conditions), computes per-file deltas, and emits PR-time gating verdicts. Use when the existing CI emits Cobertura XML - typical for JVM-heavy stacks and tools that ship Cobertura as a default reporter.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

87%

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

The body is token-efficient, highly actionable, and well-organized, with strong anti-pattern and limitation sections. The main weakness is the diff/gate workflow, which is underspecified inline and lacks an explicit validation checkpoint.

Suggestions

Inline the diff-then-gate procedure instead of deferring to `lcov-analysis` Step 4/5, so the gating workflow is self-contained.

Add an explicit validation checkpoint (e.g., 'verify the parse produced expected file count before running the gate') for the batch gating operation.

Reconcile the inline `scripts/parse_cobertura.py` and `scripts/coverage_gate.py` references with the absence of bundle files — either ship them under `scripts/` or note they are illustrative.

DimensionReasoningScore

Conciseness

Lean and dense — schema table, sample XML, executable code, anti-patterns and limitations with no padding about what coverage is; only minor redundancy is the tool-emitter list repeated across Overview and 'When to use'.

3 / 3

Actionability

Provides fully executable, copy-paste-ready code: `parse_cobertura.py`, the condition-coverage regex, `diff`, `normalize_cobertura`, and CI YAML snippets.

3 / 3

Workflow Clarity

Steps 1-6 are sequenced, but the critical diff/gate step defers detail ('The same shape as `lcov-analysis` Step 4 / Step 5') and there is no explicit validation checkpoint for the batch gating operation, capping it at 2.

2 / 3

Progressive Disclosure

Well-organized single-file skill with clearly signaled references to sibling skills and external DTD sources; no deep nesting and easy navigation, satisfying the simple-skill allowance.

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.

The description is specific, trigger-rich, and complete with an explicit 'Use when' clause. It cleanly distinguishes itself from sibling coverage-format skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Parses Cobertura XML coverage reports', 'Walks the coverage-04 DTD structure', 'computes per-file deltas', 'emits PR-time gating verdicts' — matching the top anchor.

3 / 3

Completeness

Explicitly answers both what (parse, walk DTD, deltas, gating) and when ('Use when the existing CI emits Cobertura XML'), with a clear trigger clause.

3 / 3

Trigger Term Quality

Strong natural-term coverage a user would say — 'Cobertura XML coverage reports', 'JaCoCo', 'coverage.py', 'Istanbul / Jest', 'coverlet' — plus an explicit 'Use when the existing CI emits Cobertura XML' trigger.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (JVM-canonical Cobertura XML), is third-person, and disambiguates from sibling `lcov-analysis`, making conflict unlikely.

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

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents