CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-mutation-testing

Validate that an Antithesis property catalog can actually catch bugs. For each safety property, inject one realistic mutant into the SUT, run it, and confirm the targeted property fires. Diagnoses survivors as a bad mutant, bad oracle, bad workload, or bad property, and routes fixes back to antithesis-workload or antithesis-research. Use once the harness is built and a baseline run is green.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-engineered orchestration skill: workflows are explicitly sequenced with validation gates and resume logic, detail is properly pushed to real, well-signaled one-level-deep reference files, and scripts named in the body all exist in the bundle. The only minor gaps are occasional trimmable rationale and command invocations that live in references rather than inline.

Suggestions

Add a brief quick-reference of exact one-line script invocations (fork.sh, sync-patches.sh, select-mutant.sh, verify-mutant.sh) so the most common steps are copy-paste ready without opening references/mutation-harness.md.

Tighten justification sentences (e.g. the baseline-gate and Sometimes-class rationale) to a rule plus a single-clause reason, trusting the reader with the why behind each gate.

DimensionReasoningScore

Conciseness

The body is dense, high-signal, and skill-specific — no general-concept padding — but justification prose such as "Mutation testing on a buggy SUT measures nothing: you cannot tell a property that fired because of your mutant from one that was already failing" and the layered qualifier sentences around scoping could occasionally be trimmed to a rule plus a one-line reason.

4 / 5

Actionability

Guidance names concrete scripts and flags ("verify each mutant locally with `verify-mutant.sh`", "export them with `sync-patches.sh`", "launched with a dedicated `--source` and `--ephemeral`") plus exact artifact paths, but exact command invocations are deferred to reference files rather than being copy-paste ready inline.

4 / 5

Workflow Clarity

Three explicitly sequenced workflows (First sweep, Iterate after a sweep, Resume a stopped sweep) with strong validation checkpoints — the baseline gate, local verification before spending run budget, the two-branch re-run rule — and a Self-Review checklist providing feedback loops, matching the exemplar anchor.

5 / 5

Progressive Disclosure

Clear section structure with a Reference Files table mapping each of the seven references (all present on disk) to a when-to-read condition, one-level-deep references cited with section titles (e.g. "references/sweep-and-verdicts.md, 'Attributing a falsification'"), and every cited script present in assets/mutation-testing/.

5 / 5

Total

18

/

20

Passed

Description

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

The description is specific, complete, and clearly differentiated: it names concrete actions across the whole workflow and an explicit use-when condition tied to harness readiness. The only gap is a few missing natural synonyms (e.g. "mutation testing", "kill") in its trigger vocabulary.

DimensionReasoningScore

Specificity

"inject one realistic mutant into the SUT, run it, and confirm the targeted property fires" plus "Diagnoses survivors as a bad mutant, bad oracle, bad workload, or bad property, and routes fixes back to antithesis-workload or antithesis-research" lists multiple concrete actions covering the full validate-diagnose-route lifecycle.

5 / 5

Completeness

Both halves are explicit: the what (validate the catalog by injecting mutants, diagnosing survivors, routing fixes) and the when ("Use once the harness is built and a baseline run is green") with concrete trigger conditions.

5 / 5

Trigger Term Quality

Strong natural terms within the niche ("mutant", "safety property", "survivors", "baseline run is green") but a few common phrasings a user might say — "mutation testing" itself, "kill", "caught" — are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Validate that an Antithesis property catalog can actually catch bugs" carves a clear niche, and explicit routing to sibling skills ("routes fixes back to antithesis-workload or antithesis-research") plus the post-baseline timing keeps it distinct from catalog-building, setup, and triage skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

antithesishq/antithesis-skills

Path

antithesis-mutation-testing/SKILL.md

Reviewed

Table of Contents

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.