skill-coach

Activation precision comes from clear NOT clauses and specific trigger words in your Skill's instructions. Define what problems your Skill does NOT solve and use domain-specific language to distinguish your Skill from related ones, reducing unintended triggers.

Shibboleths are expert-domain knowledge that distinguishes specialists from generalists. Encoding them into Skills ensures your instructions reflect real expertise, enabling Claude to activate with authority and handle nuanced requests that novice prompts would miss.

Use Skill Coach to review activation precision, verify frontmatter compliance (name, description, allowed-tools), check SKILL.md length stays under 500 lines, add anti-pattern documentation with concrete fixes, and validate against test cases to ensure reliability.

Document common mistakes users make with your Skill's domain—incorrect usage patterns, edge cases, and misconceptions—paired with concrete fixes. This guidance prevents activation misuse and teaches users when and how your Skill applies correctly.

Yes. Skill Coach guides lifecycle management and improvement of existing Skills through validation scripts and changelogs. Audit for missed shibboleths, add NOT clauses to reduce false activations, and refresh anti-patterns as your domain evolves.

Progressive disclosure layers Skill complexity—start with core activation criteria and essential triggers, then reveal edge cases, anti-patterns, and advanced shibboleths. This structure lets users adopt your Skill gradually while maintaining activation precision.