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.

72

Quality

91%

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

88%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 dense, actionable body with executable XML, concrete thresholds, and a strong validation feedback loop in the worked example. It is held back from a top score by duplicated XML blocks and one broken reference (references/cobertura.md).

Suggestions

Remove the duplicated <rules> XML (it appears in both the plugin block and the 'Gating with the check goal' section) - reference one canonical instance to tighten conciseness.

Fix or delete the references/cobertura.md citation in the References section; the file is not present in the bundle, creating a dangling reference.

Consider consolidating the repeated explanations of the prepare-agent/report/check goals into a single statement to reduce restatement.

DimensionReasoningScore

Conciseness

Mostly efficient, assuming Claude's familiarity with Maven/JVM basics and using dense tables and code blocks, but the full <rules> XML is duplicated (plugin block and gating section) and the three-goal explanations are restated, offering trim opportunities that keep it short of anchor 5.

4 / 5

Actionability

Provides complete executable XML plugin blocks, concrete ./mvnw -B verify commands, specific thresholds (0.80/0.70/5), real report paths, and a worked example with a copy-paste-ready failure-and-remediation scenario covering the common cases.

5 / 5

Workflow Clarity

The 'How to use' and 'Worked example' sections give a clearly sequenced process with an explicit validation feedback loop - build fails on the BRANCH rule, inspect the red branches, add tests, re-run verify until check passes - for a build-gating operation.

5 / 5

Progressive Disclosure

A clear overview with well-signaled one-level-deep references to the existing references/gradle-parsing-and-ci.md, but the References section also cites references/cobertura.md, which does not exist in the bundle, a minor organization defect that keeps it below anchor 5.

4 / 5

Total

18

/

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, specific description that explicitly states both capabilities and trigger conditions with concrete tool and build-system names. Minor room for improvement in natural-language synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - wiring the agent via prepare-agent, generating reports via the report goal, gating via the check goal with element/limit/minimum rules, parsing the six native counters, and converting JaCoCo XML to LCOV/Cobertura - giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (configures JaCoCo: wires agent, generates reports, gates build, parses counters, converts formats) and 'when' via a concrete 'Use when...' clause naming Maven/Gradle JVM builds wanting the canonical coverage tool or format conversion.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms like 'coverage', 'Maven / Gradle', 'JVM', and 'canonical JVM coverage tool', but it leans technical and misses common synonyms such as 'code coverage', so it does not reach comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (JaCoCo, the canonical JVM coverage tool, on Maven/Gradle) with distinct, specific triggers and minimal overlap risk with other 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.

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