Individual skill

skill-tester

Empirically tests a skill with subagent scenarios to verify it fires on the right prompts, stays silent on the wrong ones, and performs its job when loaded. Use when validating a new or modified SKILL.md before publishing - "test this skill", "does this trigger correctly", "verify the skill works". Do NOT use to statically grade or rewrite skill quality (use skill-auditor) - this runs live behavioral tests.

skills/skill-tester/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Skill Tester

Verifies empirically that a skill fires on the right prompts, stays silent on unrelated ones, and produces the behavior its body promises when loaded. Static review (skill-auditor) judges the text; this skill judges the behavior. A skill that reads perfectly and never fires is still broken.

## Inputs to collect

1. The SKILL.md under test, from source.
2. The neighbor skills whose territory borders it (for negative scenarios).
3. The intended user phrasing, if the author collected any - real phrasing makes the best positive scenarios.

## Operating procedure

### Step 1 - Write the scenario matrix
Back to top