skill-authoring-workflow

To turn workshop notes into compliant SKILL.md artifacts, run scripts/build-a-skill.sh or scripts/add-a-skill.sh on raw drafts, then complete Phase 3-5 validation and README updates before committing the new skill.

The best way to validate skill metadata and triggers is executing built-in validators during Phase 3-5, running test-a-skill checks, and enforcing schema rules to prevent repo breakage before final integration.

Preflight checking prevents duplicate skills by searching for overlapping skills in the repository, allowing contributors to decide the right artifact type and avoid duplication before drafting begins.

Yes, you can package skill assets into zip files for Claude uploads during the integration and packaging phase, optionally zipping assets while adhering to workshop-facilitation protocols.

Updating README tables matters when adding a new skill because it resolves references, updates counts, and maintains catalog integration, preventing repo breakage caused by inconsistent documentation.

You need definition-of-done checks for PM skill authoring whenever maintaining or shipping skills, ensuring structured validation, section order compliance, and metadata schema rules are fully met.