skill-development

Create a directory under the plugin's skills/ folder containing a SKILL.md file with YAML frontmatter defining name and description. Follow the six-step process: understand use cases, plan reusable resources, create the structure, write SKILL.md, validate, and iterate.

Write the description in third person starting with "This skill should be used when..." and include specific trigger phrases users would say, such as "create a hook" or "configure settings". Avoid vague or second-person descriptions.

Progressive disclosure is a three-level loading system: metadata stays always in context, the SKILL.md body loads when the skill triggers, and bundled resources load only as needed. Keep SKILL.md between 1,500 and 2,000 words and move detailed content to references/.

Use scripts/ for executable code requiring deterministic reliability or that gets rewritten repeatedly, such as validation utilities. Use references/ for documentation Claude should read while working, like schemas, API docs, or detailed patterns.

Skills fail to trigger when the description lacks specific trigger phrases or uses vague language. Rewrite the description in third person with concrete phrases users would actually say, then test with expected queries.