{{SKILL_NAME}}

To create new skills from spec documents, you can use a template-driven approach that converts formal requirements into ready-to-use Skill Units. This enforces YAML frontmatter with name and description in SKILL.md, a descriptive body for activation instructions, and optional folders like scripts/ and references/ for on-demand resources.

The standard SKILL.md structure for skill creation requires YAML frontmatter containing the name and description fields, followed by a descriptive body for activation instructions. This enforces project-wide conventions for naming and descriptions to improve discovery and onboarding across teams.

You generate a skill blueprint from functional requirements by preparing a spec file with fields for name and description, placing SKILL.md at the root of the new Skill Unit, and running the skill creation workflow to produce a skeleton with default structure ready for activation.

Yes, skill scaffolding supports optional folders for scripts, references, and assets. These on-demand resources are generated alongside the SKILL.md file to provide a complete skeleton structure for the new Skill Unit based on your spec.

The best way to standardize skill creation across teams is by enforcing project-wide conventions for naming and descriptions through a template-driven generation process. Converting functional specifications into ready-to-run Skill Units accelerates rapid prototyping and improves knowledge transfer.