CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pitest-mutation

Configures PIT (PITest) for mutation testing of JVM projects (Java, Kotlin via the Kotlin plugin) - wires the `pitest-maven` or `pitest-gradle-plugin` with `mutationThreshold`, `coverageThreshold`, target classes/tests filtering, runs `mvn pitest:mutationCoverage`, parses the HTML + XML reports. Use when the JVM suite needs mutation-quality verification - the canonical Java mutation testing tool, fast (PIT analyzes "in minutes rather than days").

75

Quality

94%

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

85%

Reviews 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 and well-structured with a clear workflow and properly offloaded reference material. Its only weakness is mild verbosity from restating basic mutation-testing concepts and duplicating the step list as both a summary and detailed sections.

Suggestions

Trim the Overview's quoted definition of mutation testing and the 'killed vs lived' explanation; Claude already knows these concepts - keep only the speed-differentiation claim.

Collapse the 'How to use' 7-item summary into the detailed Step 1-7 sections (or vice versa) to remove the parallel restatement of the same sequence.

Move the inline 'fast (analyzes in minutes rather than days)' claim to a single location instead of repeating it across the description and body.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code blocks, but the Overview quotes PIT explaining mutation testing and killed-vs-lived mutants (concepts Claude already knows) and the 'How to use' numbered list previews the Step 1-7 sections, creating redundancy.

2 / 3

Actionability

Provides fully executable, copy-paste-ready Maven XML, Gradle config, bash commands, and CI YAML with concrete values, satisfying the executable-code anchor.

3 / 3

Workflow Clarity

A clear Step 1-7 sequence pairs with an explicit feedback loop - 'For each surviving mutant, add or strengthen a test until it is killed' - and a worked example showing survivor detection, fix, and re-run, matching the validation-checkpoint anchor.

3 / 3

Progressive Disclosure

The SKILL.md body is an overview that offloads pitfalls to a real, clearly signaled one-level-deep reference (references/pitest-pitfalls.md, verified present), with content appropriately split and easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and clearly distinguishes the skill's niche with explicit 'what' and 'when' guidance. It is concise despite the density and uses natural trigger terms throughout.

DimensionReasoningScore

Specificity

Names several concrete actions - 'wires the pitest-maven or pitest-gradle-plugin with mutationThreshold, coverageThreshold, target classes/tests filtering, runs mvn pitest:mutationCoverage, parses the HTML + XML reports' - matching the multi-action anchor.

3 / 3

Completeness

Explicitly states both what it does (configures/wires/runs/parses) and when to use it via the 'Use when the JVM suite needs mutation-quality verification' clause, satisfying both halves of the anchor.

3 / 3

Trigger Term Quality

Covers the natural terms a user would say for this need - 'mutation testing', 'PIT', 'PITest', 'JVM projects', 'Java', 'Kotlin' - with good variation rather than jargon-only language.

3 / 3

Distinctiveness Conflict Risk

A narrow, well-defined niche (PIT mutation testing for JVM projects) with distinct tool/trigger vocabulary makes conflict with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents