mutation-test-runner
Mutation Test Runner - Auto-activating skill for Test Automation. Triggers on: mutation test runner, mutation test runner Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mutation-test-runner36
Quality
3%
Does it follow best practices?
Impact
100%
1.02xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/mutation-test-runner/SKILL.mdDiscovery
7%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 description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe any concrete capabilities, lacks natural trigger terms users would say, and provides no guidance on when to activate. The repeated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Runs mutation tests against code, analyzes surviving mutants, generates mutation coverage reports, identifies weak test cases'
Add a 'Use when...' clause with natural trigger terms like 'mutation testing', 'test quality', 'mutant analysis', 'test coverage gaps', 'pitest', 'stryker'
Include file types or contexts that trigger activation, e.g., 'Use when working with test suites, analyzing test effectiveness, or when user mentions mutation score or mutant survival'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Mutation Test Runner') and category ('Test Automation') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of running tests, analyzing mutations, generating reports, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'mutation test runner' repeated twice, which is redundant and overly narrow. Missing natural variations users might say like 'mutation testing', 'mutant analysis', 'test coverage', 'kill mutants', or tool-specific terms like 'pitest', 'stryker'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'mutation test' is a somewhat specific domain, the lack of detail about what distinguishes this from general test automation skills creates potential overlap. The category mention 'Test Automation' suggests it could conflict with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder template with no actual content about mutation testing. It contains only generic boilerplate describing what a skill should do without providing any concrete guidance, code examples, tool recommendations (like Stryker, PITest, mutmut), or workflows for running mutation tests.
Suggestions
Add concrete code examples showing how to set up and run mutation testing with specific tools (e.g., Stryker for JS, PITest for Java, mutmut for Python)
Include a clear workflow: 1) Install mutation testing tool, 2) Configure mutation targets, 3) Run mutation tests, 4) Interpret mutation score results
Remove generic boilerplate like 'provides step-by-step guidance' and replace with actual step-by-step guidance
Add specific configuration examples and common mutation operators/patterns to look for in results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about mutation testing. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, examples, or executable instructions for mutation testing. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The content only describes trigger phrases and vague capabilities without any actual process for running mutation tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to external files, no organized sections with actual content, just placeholder-style descriptions. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- 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.