write-a-skill

To standardize skill creation, use a SKILL.md template with YAML frontmatter containing name and description, plus optional metadata like tags and category. This enforces consistent documentation and ensures skills can be discovered and loaded reliably.

A SKILL.md file requires YAML frontmatter with name and description fields, followed by main content describing capability and usage. Optional metadata includes tags and category, with supporting directories like scripts/ and assets/ for organizing deterministic components.

Organize optional resources by placing deterministic scripts in a scripts/ directory, references in a references/ directory, and assets in an assets/ directory. You can also add REFFERENCE.md and EXAMPLES.md files to provide additional context and examples.

Yes, you can use optional frontmatter metadata like tags and category to improve skill discovery across teams. Standardizing this metadata ensures consistent documentation and makes skills easier to find and load reliably.

The best way to onboard new skills is to create a skill folder with a SKILL.md file containing required frontmatter and a concise description. Add optional supporting files like REFFERENCE.md and EXAMPLES.md as needed to maintain clarity for future maintenance.

No, optional directories like scripts/, references/, and assets/ are not required. A skill only needs a SKILL.md file with YAML frontmatter and a description to be ready-to-use, while optional directories help organize deterministic components and content.