Best-Practice Creator

To validate YAML frontmatter fields for best-practice files, this Skill enforces required metadata fields (id, name, whenToUse, version) and checks overall file structure during new submissions and updates to ensure catalog integrity. It runs automated checks against the repository standards.

To prevent duplicate entries in a best-practice catalog, this Skill performs pre-flight checks against the existing catalog and repository entries to detect overlaps and conflicts before a new file is created or updated.

The best way to maintain cross-references in a best-practice library is to use automated catalog maintenance workflows that update or append entries and validate cross-references to ensure they remain consistent across the repository.

You can check if a new best-practice submission conflicts with existing catalog entries by running this Skill's pre-flight discovery integration, which scans existing files and the catalog to detect overlaps and conflicts before submission.

Yes, the best-practice validation workflow integrates with skills/*/SKILL.md files to inform scope, naming, and consistency, ensuring new best-practice entries align with existing skill definitions across the repository.

The required frontmatter fields for a valid best-practice file submission are id, name, whenToUse, and version. The Skill enforces these YAML frontmatter requirements during creation and updates to maintain catalog consistency.