skill-authoring-workflow

To validate SKILL.md frontmatter before publishing, use an automated workflow that enforces required fields like name, description, and intent while checking metadata size limits and section order. This ensures repository standards are met before committing new skills.

The best way to turn raw PM content into a compliant repository skill is using a guided generation workflow with preflight and duplicate-checks. It transforms rough notes into a validated SKILL.md asset, ensuring frontmatter validity and cross-reference resolution before publishing.

Yes, you can automate skill creation from workshop notes without breaking repository standards by applying a validation workflow. It automatically applies preflight checks, enforces section order, and verifies metadata size limits to generate a compliant SKILL.md file.

Cross-reference validation scripts work when updating existing repository skills by resolving internal links and dependencies before committing. This ensures that updates remain consistent and the skill catalog stays reliable without introducing broken references.

Your new skill fails the preflight duplicate-check during generation because the workflow detects a conflicting skill name or intent already published in the repository. This prevents adding overlapping skills and maintains catalog reliability before you proceed with validation.