Content
81%Weight 40%Scale 1-5Reviews 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 a complete Maven plugin config, a worked failure/recovery example, and a valuable anti-patterns table, and it correctly pushes Gradle/parsing/CI detail into a real reference file. It is held back by a six-counter definition table that re-teaches concepts Claude already knows, triplicate rule XML, and one dangling reference path (references/cobertura.md).
Suggestions
Replace the six-counter definition table with a one-line list of counter names plus the complexity formula; the quoted definitions (e.g. 'A source line is considered executed when at least one instruction...') re-explain what Claude already knows.
Show the check-rule XML once: the 'Wire the Maven plugin' and 'Gating with the check goal' sections both render full BUNDLE INSTRUCTION/BRANCH limit blocks, and the compact snippet repeats them a third time — keep only the two-rule pattern with excludes.
Fix the References section: 'lcov-analysis (references/cobertura.md)' points to a file not present in this bundle — clarify it belongs to the sister skill, and consolidate the five repeated links to references/gradle-parsing-and-ci.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The six-counter definition table ("The smallest unit JaCoCo counts are single Java byte code instructions", "A source line is considered executed when...") re-explains concepts Claude already knows, the INSTRUCTION/BRANCH limit XML appears three times (plugin block, gating section, compact snippet), and the pinned "0.8.13" version is time-sensitive. Not 2 because most sections (anti-patterns, worked example, CI) are tight and every token there earns its place. | 3 / 5 |
Actionability | Fully executable guidance: complete copy-paste plugin XML, `./mvnw -B verify`, report paths, the value-options table, and a worked example covering the common failure case ("the build fails on the BRANCH rule (minimum 0.70), naming the bundle and the missed limit"). Not 4 because concrete examples cover the common cases end-to-end with no gaps. | 5 / 5 |
Workflow Clarity | Clear 4-step sequence in 'How to use' plus a worked example with an explicit feedback loop: build fails on the BRANCH rule → open index.html → drill into red branches → add tests → "re-run `./mvnw -B verify` until `check` passes". Not 4 because error recovery and validation checkpoints are explicit rather than implicit. | 5 / 5 |
Progressive Disclosure | Good split: Gradle config, XML parser, gating table, and CI job are correctly deferred to the one-level-deep references/gradle-parsing-and-ci.md, which exists and contains that content. Not 5 because the References section cites "references/cobertura.md", which does not exist in this bundle (a dangling pointer), and the same reference file is linked five separate times. Not 3 because content placement is otherwise appropriate and clearly signaled. | 4 / 5 |
Total | 17 / 20 Passed |