skill-authoring

To automate repeatable agent workflows, you create a reusable skill definition by writing a SKILL.md file with required frontmatter like name and description, then place it under the skills directory to persist instructions across sessions.

SKILL.md frontmatter is required metadata containing a name and description that defines how a skill guides agent behavior and triggers. You need it when codifying repeatable tasks or saving instructions for future automation sessions.

Yes, you can compose complex workflows by layering multiple skills to share best practices across projects. This approach enables scalable automation by combining standalone skill definitions to extend agent capabilities.

No dependencies are required to codify procedures as standalone skills. You write a SKILL.md file with frontmatter, and can optionally include references to scripts, assets, or references as needed to support the workflow.

The best way to save guidelines for future sessions is creating a frontmatter-driven SKILL.md entry that defines concise triggers and behaviors, reducing repetitive tasks by persisting instructions as a reusable skill.

If a skill definition does not persist or trigger correctly, it likely lacks the required frontmatter fields name and description in the SKILL.md file, or the file is not properly placed under the skills directory for session retrieval.