Testing Skills With Subagents

When to use

• Before deploying a new skill
• After editing an existing skill
• Skill enforces discipline that could be rationalized away

Skip when

• Pure reference skill → no behavior to test
• No rules that agents have incentive to bypass

Related

Complementary: ring:writing-skills, ring:test-driven-development

Testing skills is TDD applied to process documentation.

Run scenarios without the skill (RED — watch agent fail), write skill addressing those failures (GREEN), then close loopholes (REFACTOR).

Prerequisite: Understand ring:test-driven-development first. Complete worked example: examples/CLAUDE_MD_TESTING.md.