create-skill

To create a reusable skill blueprint, you define a SKILL.md file with mandatory name and description in the YAML frontmatter, followed by a Markdown body for operational guidance to ensure consistent packaging.

The best way to scaffold a self-contained skill unit is to use a structured workflow that generates a canonical SKILL.md alongside optional bundles like scripts, references, and assets, keeping context lean.

Yes, YAML frontmatter is required when building a skill template. The blueprint enforces mandatory name and description fields within the frontmatter to standardize the skill metadata.

Yes, you can include optional scripts and references when creating skill scaffolding. The blueprint supports on-demand bundles for assets, scripts, and references to enable deterministic behavior while keeping context lean.

Your skill unit structure lacks consistency because it misses a standardized blueprint. Defining a canonical SKILL.md with mandatory frontmatter and structured bundles solves this by ensuring reusability across projects.