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.
Highly actionable, executable guidance with a clearly sequenced, validated workflow and a well-linked pitfalls reference. The main weaknesses are redundant concept and trigger explanations Claude does not need, duplicated step summaries, stale-prone pinned versions, and a body heavier than an overview should be.
Suggestions
Remove the Overview blockquotes explaining what mutation testing is and the "When to use" bullets that duplicate the frontmatter description - Claude already knows the concept and the triggers (conciseness).
Drop the "How to use" 7-step summary since Steps 1-7 repeat it, and replace pinned versions (1.17.0, 1.15.0, 1.2.1) with "latest stable" guidance or a single clearly-marked version note (conciseness).
Move the CI workflow YAML (Step 6) and the Gradle configuration into a references/ file alongside pitest-pitfalls.md so SKILL.md stays a lean overview (progressive disclosure).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, actionable config, but it includes explanation Claude already knows ("PIT is a mutation testing system... automatically introduces faults"), a "When to use" section duplicating the frontmatter description, a "How to use" list duplicating Steps 1-7, and hard-pinned version numbers (1.17.0, 1.15.0, 1.2.1) that will go stale. Fits "mostly efficient but could be tightened" rather than the minor-instances anchor at 4. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready guidance: complete Maven plugin XML, Gradle `pitest` block, `mvn pitest:mutationCoverage` commands, GitHub Actions YAML, and a concrete worked example (mutating `total >= 50` to `total > 50`, fixed by a `total == 50` boundary test) covering the common Maven/Gradle/JUnit 5 cases. | 5 / 5 |
Workflow Clarity | Clear install-to-iterate sequence with explicit validation gates ("mutationThreshold... fail the build") and an explicit feedback loop ("For each surviving mutant, add or strengthen a test until it is killed"), demonstrated end-to-end in the worked example. Matches the top anchor with validation steps and error-recovery loops rather than "most checkpoints" at 4. | 5 / 5 |
Progressive Disclosure | Good structure with a clearly signaled one-level-deep reference ([references/pitest-pitfalls.md] exists, matches the body link, and nests no further), but the ~190-line body inlines content that could be split out (CI YAML, Gradle config, concept quotes), leaving minor organization gaps between "good structure" and a truly lean overview. | 4 / 5 |
Total | 17 / 20 Passed |