mutation-test-suite-optimizer
Optimize test suites using mutation testing to maximize mutation kill rate with minimal tests. Use when you need to reduce test suite size while maintaining quality, identify redundant tests, improve mutation coverage, or validate test effectiveness. The skill analyzes test coverage, execution intervals, and redundancy using mutation operators, selects or generates a minimal subset of tests that maximizes mutation kill rate, and outputs an optimized test suite with detailed reports showing killed and surviving mutants. Supports multiple programming languages and mutation testing frameworks.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill mutation-test-suite-optimizer81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is an excellent skill description that clearly articulates specific capabilities, provides explicit trigger conditions with a 'Use when...' clause, and uses domain-appropriate terminology that users would naturally employ. The description is comprehensive yet focused, covering the what, when, and how without unnecessary verbosity. The mutation testing focus creates a clear, distinctive niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes test coverage, execution intervals, and redundancy using mutation operators', 'selects or generates a minimal subset of tests', 'outputs an optimized test suite with detailed reports showing killed and surviving mutants'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Optimize test suites using mutation testing...analyzes test coverage...selects or generates a minimal subset...outputs an optimized test suite') AND when ('Use when you need to reduce test suite size while maintaining quality, identify redundant tests, improve mutation coverage, or validate test effectiveness'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'mutation testing', 'test suite', 'mutation kill rate', 'redundant tests', 'mutation coverage', 'test effectiveness', 'surviving mutants', 'killed mutants'. These cover the domain vocabulary well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focusing specifically on mutation testing optimization. The specific terminology ('mutation kill rate', 'mutation operators', 'surviving mutants') clearly distinguishes it from general testing or code quality skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured with good CLI examples and a clear output format. However, it lacks workflow clarity for the optimization process—there's no step-by-step sequence showing how to interpret results, handle surviving mutants, or validate the optimized suite. The actionability is limited by referencing scripts without explaining their implementation or dependencies.
Suggestions
Add a clear numbered workflow showing the full optimization process: run analysis → review report → handle surviving mutants → validate optimized suite → integrate into CI
Include validation steps such as 'verify optimized suite still passes' and 'review surviving mutants for test gaps'
Clarify dependencies and setup requirements for the scripts/optimize.py tool, or provide the actual implementation
Add a section on interpreting and acting on surviving mutants with concrete examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what mutation testing is or how it works conceptually. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides concrete CLI commands and example output, but references scripts (scripts/optimize.py) that may not exist. The commands are copy-paste ready but lack context on setup, dependencies, or what the script actually does internally. | 2 / 3 |
Workflow Clarity | No clear multi-step workflow is defined. The skill describes what gets optimized and shows commands, but lacks a sequenced process with validation checkpoints. There's no guidance on verifying results, handling failures, or iterating on surviving mutants. | 1 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. For a skill of this complexity, references to detailed documentation on mutation operators, framework-specific guides, or troubleshooting would improve navigation. | 2 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.