write-skill

Create a SKILL.md file with required YAML frontmatter (name, description fields), keep the body under 200 lines, and organize supporting content into scripts/, references/, and assets/ directories. This structure ensures consistency and token efficiency across your Skill implementation.

Write a concise description that includes triggers and clearly states the problem solved, following best practices for YAML frontmatter. Use progressive disclosure to keep descriptions lean while offloading detailed examples and guidance to references/, maximizing token efficiency.

Use the included validation script to check for YAML frontmatter compliance, required name and description fields, body length constraints, and correct directory layout. This ensures your Skill meets functional requirements before deployment.

This Skill applies to both creating new Skills and refactoring existing ones. It provides standardized templates and best-practice guidance to ensure all Skills—whether new or mature—meet structural, content, and optimization standards.

Lean SKILL.md files with progressive disclosure reduce token overhead and improve readability. By moving detailed examples, extended documentation, and reference material to separate files, you create efficient Skills that load faster and communicate intent clearly.

A complete Skill includes SKILL.md with frontmatter, a scripts/ directory for core logic, a references/ directory for documentation and examples, and an assets/ folder for media or config files. This layout supports automation, best practices, and lean design.