Skill Testing

An untested skill is a skill that silently breaks. Build a test harness covering frontmatter, content, and activation, run it in CI, and you'll catch regressions long before users file bugs.

When to Use

• Setting up a new skills repository
• Adding skills to an existing repo without test coverage
• Debugging why a skill exists but never activates
• Reviewing PRs that add or modify skills

Three Layers of Testing

1. Static validation — frontmatter parses, required fields present
2. Content lint — length, structure, code-block sanity
3. Activation testing — does the skill fire on realistic queries?

Layer 1: Static Validation