skill-creator

To write a high-quality SKILL.md file, include a frontmatter contract with name and description fields, then structure the body using markdown for modularity, progressive disclosure, and portability across platforms.

The required yaml frontmatter for a Skill Unit must include name and description fields, while optional fields can be added to ensure proactive descriptions, progressive disclosure, and portability across platforms.

Package AI agent skills by creating a directory layout with SKILL.md as the entry point, then add optional supporting files like scripts, references, and assets to enable flexible, on-demand loading.

The best way to validate frontmatter and ensure skill quality is to apply a 15-point checklist that reviews frontmatter rules, body-length guidance, supporting-file strategies, and portability patterns.

Yes, you can use modular writing patterns and progressive disclosure in your SKILL.md to improve skill portability across platforms, ensuring flexible, on-demand loading of supporting files.

You should avoid optional supporting files in a skill directory when the SKILL.md body alone satisfies the quality checklist, as unnecessary scripts or assets can reduce portability and hinder on-demand loading.