mutation-testing

Set up and run mutation testing with PIT (pitest) on a Gradle project, and read the mutation score. Use this skill whenever the user wants mutation testing added to a build, configured, run or re-run, wants a mutation score or a mutation report interpreted, asks why a particular mutant survived, or asks what should be excluded from mutation analysis, or wants something added to those exclusions — in any language, and whether or not the tool is named. Also use it when the task calls for it: checking test quality rather than coverage — a high JaCoCo number can hide tests that assert nothing.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A well-structured, concise procedural skill body with clear skip-checkpoints, an error-recovery loop, and properly signaled one-level-deep references that are real files. The only minor gap is that the core runnable commands are factored into the reference files rather than inlined.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — it explains only the why of each skip-check and never pads with what mutation testing or PIT is — so every token earns its place, matching the 5 anchor.	5 / 5
Actionability	It provides a concrete executable grep command and precise 'follow references/X.md' pointers, but most actual run/configure commands live in the referenced files, leaving minor gaps consistent with the 4 anchor.	4 / 5
Workflow Clarity	A clear 4-step sequence where each step carries an explicit 'Skip if' validation checkpoint, plus a stale-entry error-recovery feedback loop ('If step 3 fails… the entry was stale: say so, run this step after all'), matches the 5 anchor.	5 / 5
Progressive Disclosure	The body is an overview that delegates detail to one-level-deep, clearly signaled references (configuration.md, add-exclusion.md, usage.md) and a real script, all verified to exist, matching the 5 anchor.	5 / 5
	Total	19 / 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.

A strong, third-person description that comprehensively covers concrete capabilities and trigger conditions with natural user phrasing and tool synonyms. It clearly distinguishes itself from generic coverage/test skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — set up, configure, run/re-run mutation testing, read the score, interpret reports, manage exclusions — covering the domain comprehensively, matching the 5 anchor.	5 / 5
Completeness	It states a clear 'what' (set up and run mutation testing, read the score) and an explicit 'when' via 'Use this skill whenever…' and 'Also use it when the task calls for it…' with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Natural user phrases ('mutation testing', 'mutant survived', 'mutation score', 'excluded from mutation analysis') plus synonyms and tool names (PIT/pitest, Gradle, JaCoCo) give comprehensive coverage as the 5 anchor requires.	5 / 5
Distinctiveness Conflict Risk	A clear niche (mutation testing with PIT on Gradle) with distinct triggers — 'why a particular mutant survived', 'JaCoCo coverage hiding non-asserting tests' — yields minimal conflict risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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.

Repository: Amplicode/spring-skills
Path: skills/mutation-testing/SKILL.md
Commit: bf19b3c

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.