manage-skills

Auditing existing skills involves reviewing frontmatter structure for required name and description fields, checking optional fields like disable-model-invocation and argument-hint, and verifying repository conventions for proper naming, placement, and taxonomy layer assignment.

Skill governance frontmatter requires name and description fields as mandatory structure, while optional fields include disable-model-invocation and argument-hint, ensuring consistent metadata across the repository taxonomy and skill layer placement.

To create a new skill following repository conventions, apply governance templates that enforce frontmatter structure with name and description fields, follow repository conventions for proper naming and placement, and maintain taxonomy consistency across skill layers.

Skill taxonomy and layer placement maintenance is needed during new skill creation, existing skill reviews, and repository audits to ensure proper naming, correct layer placement, and frontmatter conformance across the Claude Code skills repository.

Skill governance works without external dependencies, providing built-in auditing guidance, templates, and workflow references to standardize Claude Code skills directly within the repository using frontmatter structure and convention enforcement.

The best way to standardize skill naming and placement is to apply governance templates and auditing steps that enforce frontmatter structure, repository conventions, and taxonomy layer rules during skill creation and existing skill reviews.