skill-authoring-workflow

You can turn rough PM notes into a compliant skill manifest by running a guided wizard or content-first generator that drafts, validates, and integrates frontmatter and sections before committing.

Skill frontmatter validation requires checking name, description, intent, and type fields, while repository standards enforce compliant section order, metadata limits, and resolving cross-references.

The best way to create a new repository skill is using repo-native authoring tools like the build-a-skill wizard or add-a-skill generator to draft and validate content automatically.

Yes, you can update an existing skill manifest using a content-first workflow that applies preflight checks, drafts updates, and validates frontmatter and cross-references before integration.

You need to run preflight and validation steps for skill authoring whenever creating new repo skills or updating existing ones to ensure frontmatter is valid and cross-references resolve.

A skill manifest fails repository standards during manual edits when frontmetadata limits are exceeded, section order is non-compliant, or cross-reference checks fail to resolve properly.