CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/jacoco-analysis

Configures JaCoCo for JVM projects (Java / Kotlin / Scala / Groovy) - wires the runtime agent via `jacoco-maven-plugin` `prepare-agent`, generates per-build reports (HTML / XML / CSV) via the `report` goal, gates the build via the `check` goal with element / limit / minimum rules, parses the six native counters (instructions, branches, lines, methods, classes, cyclomatic complexity), and converts JaCoCo XML to LCOV / Cobertura when downstream tools need a different format. Use when the JVM build is Maven / Gradle and the team wants the canonical JVM coverage tool - or to convert JaCoCo output for cross-language coverage aggregation.

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

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.

The body is highly actionable with executable Maven config and a clear, validated workflow including an error-recovery loop, and it practices good progressive disclosure by offloading detail to a single well-signaled reference. The main weakness is mild verbosity from re-explaining JaCoCo counter semantics Claude already knows.

Suggestions

Tighten the six-counter definition table: keep the formula for cyclomatic complexity and any non-obvious notes, but drop or shorten definitions of lines/methods/classes that Claude already knows.

Avoid restating the 'all counters work at bytecode level' insight twice; state it once in Limitations and reference it rather than repeating the full quote in the Overview.

DimensionReasoningScore

Conciseness

Mostly lean with tight tables and executable code, but the six-counter definition table re-explains concepts Claude already knows (what a line/method/class counter is) and restates the bytecode-level insight, which could be trimmed.

2 / 3

Actionability

Provides fully executable Maven XML blocks, concrete './mvnw -B verify' commands, real threshold values, real output paths, and complete counter/value option tables that are copy-paste ready.

3 / 3

Workflow Clarity

The 'How to use' section gives a clear 4-step sequence and the 'Worked example' includes an explicit error-recovery feedback loop (branch coverage 66% fails the gate -> drill red branches -> add tests -> re-run until check passes).

3 / 3

Progressive Disclosure

SKILL.md is an overview and pushes Gradle config, the XML parser, the gating table, format conversions, and the full CI job into one clearly-signaled, one-level-deep reference file that exists and is linked repeatedly with context.

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, action-oriented, and written in third person, with an explicit 'Use when' trigger clause and good coverage of natural JVM-coverage terminology. It cleanly answers both what the skill does and when to use it without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'wires the runtime agent via prepare-agent', 'generates per-build reports (HTML / XML / CSV) via the report goal', 'gates the build via the check goal', 'parses the six native counters', and 'converts JaCoCo XML to LCOV / Cobertura'.

3 / 3

Completeness

Explicitly answers both what it does (configure agent, reports, gating, parsing, conversion) and when to use it via the explicit 'Use when the JVM build is Maven / Gradle...' clause.

3 / 3

Trigger Term Quality

Covers the natural terms a user needing JVM coverage would say: 'JaCoCo', 'JVM projects', 'coverage', 'Maven / Gradle', 'LCOV / Cobertura', and 'cross-language coverage aggregation'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (canonical JVM coverage via JaCoCo) distinct from sister skills (Cobertura / LCOV), with the conversion use scoped to JaCoCo output, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents