skill-builder

Claude Skills require pure XML structure in their SKILL.md files with specific required tags for optimal parsing and performance. This Skill guides you through proper XML tag usage, YAML frontmatter setup, and naming conventions to ensure your Skills follow platform standards and are correctly interpreted by Claude.

Skill creation follows a structured workflow: gather requirements, detect project context, research external APIs if needed, scaffold SKILL.md with YAML frontmatter, write concise XML-tagged instructions, apply progressive disclosure to keep files under 500 lines, validate structure, test with real scenarios, and create a slash command wrapper. This Skill walks you through each step.

Progressive disclosure keeps SKILL.md concise by linking detailed information to separate reference files instead of embedding everything inline. This Skill teaches you how to identify what belongs in the main file versus reference files, reducing token consumption while maintaining complete guidance and improving Skill efficiency.

Yes. This Skill includes automated validation workflows that check YAML syntax, enforce line count limits, verify required tags are present, validate naming conventions follow verb-noun patterns, and ensure reference organization meets standards. These checks catch structural issues before deployment.

Skill directories must follow verb-noun conventions like `create-*`, `manage-*`, `setup-*`, or `generate-*`. The YAML frontmatter `name` field must match the directory name, and `description` should use third-person language describing what the Skill does. This Skill enforces these naming standards during creation and validation.

Context detection determines scope: project-specific Skills serve particular workflows or codebases, while global Skills address platform-wide tasks. This Skill helps you gather requirements and analyze scope to decide which approach fits your use case, ensuring your Skill reaches the right users at the right time.