CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/pitest-mutation

Use for any question about mutation testing in Java or Kotlin, or when a JVM suite has high line coverage but may assert nothing: sets up PIT (PITest) with Maven or Gradle, target classes, mutators, mutation-score thresholds that fail the build, incremental runs, Kotlin support and the HTML and XML reports.

Quality

92%

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

81%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.

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).

DimensionReasoningScore

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

Description

100%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.

An exemplary description: an explicit "Use for..." clause with concrete scenario triggers, a dense list of specific capabilities, tool-name synonyms, and tight JVM scoping that keeps conflict risk minimal. All four dimensions sit at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities spanning setup through reporting: "sets up PIT (PITest) with Maven or Gradle, target classes, mutators, mutation-score thresholds that fail the build, incremental runs, Kotlin support and the HTML and XML reports". Coverage is comprehensive; only CI integration is unstated and "incremental runs" partially covers it, so this fits the top anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Both questions are answered explicitly: "Use for any question about mutation testing in Java or Kotlin, or when a JVM suite has high line coverage but may assert nothing" gives concrete trigger phrases, and the capability list clearly states what it does. This is the top anchor, not 4, because the "when" clause is explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered: "mutation testing in Java or Kotlin", "JVM suite has high line coverage but may assert nothing", tool-name synonyms "PIT (PITest)", and build tools "Maven or Gradle". Synonyms and scenario language are both present, matching the synonym-inclusive top anchor rather than "a few natural terms missing" at 4.

5 / 5

Distinctiveness Conflict Risk

Scoped tightly to JVM mutation testing ("mutation testing in Java or Kotlin", "JVM suite", "PIT (PITest)"), a clear niche with distinct triggers and minimal overlap risk against per-language mutation-testing siblings (Stryker, mutmut, mull). Clearly the minimal-conflict anchor, not the minor-overlap anchor at 4.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page