mcaf-skill-curation

To detect agent skill drift, inventory and compare SKILL.md frontmatter against actual folder names across .codex/skills and .claude/skills to identify structural mismatches. This process surfaces inconsistencies between documented metadata and real codebase definitions.

To validate YAML frontmatter, enforce rules ensuring the name and description fields follow required formats, proper lengths, and folder-name alignment. This removes template cruft like README.md and keeps skill folders lean.

The best way to generate available skills metadata is to run a curation workflow that audits skill folders and produces a metadata-only <available_skills> block plus a validation report. This helps agent runtimes discover current capabilities.

Yes, you can apply YAML validation across both .codex/skills and .claude/skills directories. The workflow audits both paths to align frontmatter rules, enforce folder-name matching, and remove template docs consistently.

Your agent skill folder name does not match the frontmatter name due to repository drift over time. Running a skill curation validation enforces folder-name alignment with the YAML frontmatter to resolve these mismatches.

Yes, you need the yaml dependency to parse and validate SKILL.md frontmatter rules. It enables the enforcement of proper name and description lengths and folder-name matching across skill directories.