Skill Tester
Dry-runs a skill against a test input to verify trigger detection, output shape, and side-effect safety before shipping.
Entry verified April 20, 2026
The short answer
The QA step for skill authors. Simulates invocation, checks the trigger matches, and verifies the skill doesn't accidentally write files or call APIs it shouldn't.
When to use it
Before adding a new skill to your .claude/ directory. Before sharing a skill publicly.
Setup
- 1
Save as ~/.claude/skills/skill-tester.md.
- 2
Needs a test-cases file (JSON or YAML) describing inputs + expected behaviour.
- 3
Invoke: /skill-tester <skill-name>.
Example
You: /skill-tester pivot-sweep Claude: 3 test cases. 2 pass ✓. 1 fails: tier-boundary case — treats a prompts/*.js file as Tier B instead of Tier A. Review regex.
Source & attribution
- Author
- Bryan Collins
- Licence
- MIT
- Type
- Original
Original pattern published under MIT — attribution preserved by convention, not licence requirement.
Caveats
Dry-run simulates but doesn't guarantee — ship to a test environment before production.
Browse more skills
47 skills across 10 categories, all licence-verified.