skill-authoring-workflow

To turn rough notes into a SKILL.md file, use a guided wizard or content-first generator to transform raw PM content, enforce frontmatter rules, and produce repo-compliant assets. This ensures your skill passes automated structural checks before committing.

Validating skill metadata requires running repository scripts that enforce frontmatter rules, section ordering, and trigger quality. This validation process prevents broken skills by checking structural compliance and finding duplicates before you commit updates.

You can update the README catalog automatically by running repository integration scripts during your skill authoring workflow. This packaging step validates metadata, updates the catalog, and optionally produces a zip file ready for Claude upload.

Yes, the skill authoring workflow supports workshop synthesis by converting workshop outputs and partial prompt dumps into interactive advisor skills. It applies strict validation guardrails to ensure the generated content fits the repository structure.

Manual skill editing without validation risks noncompliant assets, broken triggers, and incorrect metadata limits. Bypassing repository scripts leads to structural errors and duplicate entries, preventing successful README integration and automated checks.

To package skills for Claude upload, run the repository validation scripts to check metadata and triggers, update the README catalog, and generate a compliant zip file. This ensures your authored skill is structurally sound and ready for deployment.