creating-skills

To turn recurring agent patterns into reusable skills, you formalize repeated explanations and corrections into a new Skill Unit. This standardizes responses by creating a directory with a SKILL.md file containing required YAML frontmatter and concise instructions.

Required frontmatter when creating agent skills includes only the name and description fields in the SKILL.md YAML header. Enforcing these frontmatter standards ensures structured, on-demand loading of metadata and detailed instructions when the skill is activated.

Structure agent skills by creating a directory at agents/skills/<skill-name>/ containing a SKILL.md file. You can optionally include scripts/, references/, and assets/ subdirectories to support extended behavior, documentation, and resources for the skill.

Formalize user corrections into a skill template when you notice repeated mistakes or recurring explanations that need standardization. This reduces duplication, speeds up automation, and ensures consistent responses across future interactions by applying the guided creation process.

Yes, you can include optional resources in agent skills by adding scripts/, references/, and assets/ directories alongside the SKILL.md file. These optional resources document extended behavior and provide supplementary documentation for more complex skill usage.

The best way to standardize repeated explanations is to create a canonical Skill Unit with YAML frontmatter containing name and description fields. This guided template enforces structure, enables on-demand metadata loading, and documents optional resources for extended use.