Content
92%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.
A lean, highly actionable skill body: complete Maven/Gradle/CI configurations, a concrete boundary-mutant worked example, an explicit kill-loop workflow, and well-organized offloading of pitfalls to a single real reference file. The only slack is duplicated marketing quotes and inline version pins that could be trimmed or consolidated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most of the body earns its tokens (executable pom/gradle/CI snippets, a worked example), but there is trimmable padding: a block quote explaining what mutation testing is, the "minutes rather than days" speed claim repeated in both Overview and the description, and pinned version numbers (1.17.0, 1.15.0, 1.2.1) presented outside any deprecated/versioning section. | 4 / 5 |
Actionability | Fully executable throughout: complete `pitest-maven` plugin XML with the JUnit 5 dependency, a copy-paste Gradle `pitest {}` block, exact run commands (`mvn pitest:mutationCoverage`, `./gradlew pitest`), a GitHub Actions YAML snippet, and a concrete worked example (the `total >= 50` boundary mutant) covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 1–7 are clearly sequenced from install to CI, and the process includes an explicit feedback loop — "For each surviving mutant, add or strengthen a test until it is killed" — reinforced by the worked example's kill-verify-rerun cycle and threshold-gated build failure for validation. | 5 / 5 |
Progressive Disclosure | The SKILL.md keeps core setup/run/CI content inline and moves anti-patterns and limitations to a clearly signaled, one-level-deep reference (`references/pitest-pitfalls.md`, verified to exist), with a References section describing each link — an easy-to-navigate overview structure. | 5 / 5 |
Total | 19 / 20 Passed |