skill-scaffold

To create a SKILL.md file conforming to Skill Metadata Protocol v7, use skill-scaffold to generate the file from the canonical template, adapt archetype sections, and strip teaching-layer notes before committing.

Removing template residue when authoring skill metadata involves copying the canonical template, adapting it to your chosen archetype, and stripping all TEMPLATE NOTE teaching blocks to ensure a protocol-coherent SKILL.md specimen.

Routing eval validation defaults to absent during skill creation and only promotes to present after you successfully run the routing eval script, ensuring honest routing-eval claims in the SKILL.md metadata.

You need to run lint checks on a SKILL.md file before committing to verify protocol consistency, validate semantic-layer discipline, and ensure grounding truth sources are correctly populated.

Yes, skill-scaffold supports creating brand-new capability, workflow, router, and overlay skills by adapting the canonical template sections to the chosen archetype while maintaining protocol frontmatter.

The description field serves as a routing contract distinct from the Coverage section, which acts as a scope map; maintaining this semantic-layer discipline prevents inconsistent protocol frontmatter and inflated health claims.