skill-authoring

To create reusable agent skills, you define a new skill and document its workflow in a SKILL.md file. This file must include frontmatter with a name and description, and a body presenting the problem, features, and a quick-start line to ensure proper persistence and reuse across tasks.

The best way to standardize agent capabilities is by capturing workflows as structured, reusable skills. Sharing these skill definitions with teammates ensures consistent behavior across tasks and reduces workflow duplication.

To structure documentation for a reusable workflow, ensure the SKILL.md body presents the problem, features, and a quick-start line. The file's frontmatter must include a name and description, with optional directories to extend functionality.

Yes, you can save instructions for future sessions by drafting them as reusable skills. This persistence capability stores your structured procedures, allowing agents to access and reuse the workflows across different tasks without rewriting them.

To make a skill reusable, the frontmatter must include a name and a description. This standardization allows the system to correctly organize and persist the agent capabilities for future tasks.