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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mutation-test-runnerActivation
7%This description is severely underdeveloped, functioning more as a label than a useful description. It provides no information about what actions the skill performs, lacks natural trigger terms users would actually say, and has no guidance on when Claude should select this skill. The repetitive trigger term and boilerplate structure suggest auto-generated content without meaningful customization.
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'
Include a 'Use when...' clause with natural trigger terms like 'mutation testing', 'test quality', 'mutant analysis', 'test effectiveness', or specific tool names
Remove the duplicate trigger term and expand with variations users might naturally say when needing mutation testing help
| 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 (e.g., 'runs mutation tests', 'analyzes code coverage', 'generates mutants'). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent guidance). Only provides a category label without substance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'mutation test runner' repeated twice, which is technical jargon. Missing natural variations users might say like 'mutation testing', 'test mutations', 'code mutants', 'kill mutants', or tool names like 'pitest', 'stryker'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'mutation test' is a fairly specific testing concept that wouldn't overlap with general testing skills, the lack of detail about what specifically this skill does versus other testing-related skills creates some ambiguity. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is a placeholder template with no actual mutation testing content. It lacks any concrete guidance on mutation testing tools (like Stryker, PIT, or mutmut), configuration examples, or workflows. The content describes capabilities in abstract terms without delivering actionable instructions.
Suggestions
Add executable code examples showing how to configure and run a mutation testing framework (e.g., Stryker for JS, PIT for Java, mutmut for Python)
Include a clear workflow: 1) Install tool, 2) Configure mutation targets, 3) Run mutation tests, 4) Interpret results and improve test coverage
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual mutation testing patterns and commands
Add specific guidance on interpreting mutation scores and fixing surviving mutants
| 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 executable guidance is provided. The skill describes what it does in abstract terms but never shows how to actually run mutation tests or configure a mutation testing framework. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for running mutation tests. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with clear headers, but there are no references to detailed documentation, examples, or related files. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.