skill-authoring-workflow

To turn workshop notes into publish-ready SKILL.md files, use a guided creation workflow that converts raw PM content into validated assets. It enforces frontmatter rules, section ordering, and metadata limits while running repository scripts for structural checks.

The best way to validate skill metadata limits and frontmatter rules is through repo-native validation scripts. This process checks structural compliance, enforces a strict definition of done, and prevents broken references in your skill catalog.

Yes, you can update README catalogs when adding new skills. The workflow includes packaging and integration steps to add the skill to the README with correct counts and links after running metadata checks.

To package skills for distribution from half-finished drafts, use a content-first generator or manual tightening path. This workflow runs build and test checks, enforces section ordering, and produces a publish-ready SKILL.md asset.

Skill authoring workflows fail structural checks due to inconsistent frontmatter, incorrect section ordering, or exceeding metadata limits. Running repository validation scripts identifies these errors and enforces a strict definition of done before publishing.

No, you do not need existing documentation to create a new skill folder. The workflow supports a guided wizard for incomplete source material, allowing you to draft skills directly from raw prompt dumps or workshop notes.