skill-system-audit

You can validate YAML syntax and routing tables by auditing the skill repository, parsing SKILL.md frontmatter and ROUTING-TABLE.yaml files. This verifies that all referenced skills exist and flags archived skills mistakenly used in routing configurations.

Fragmented skills and cross-reference errors occur when active skill folders do not match the manifest list or when skill:// links point to missing files. Auditing the repository uncovers these mismatches and detects common naming errors in intents and routes.

Yes, you can apply a system audit to any skill repository using the skill:// protocol. It scans directories, manifests, and routing configurations to identify YAML validity issues and routing table corruption across the ecosystem.

To detect archived skill leakage, scan all markdown and yaml files to extract skill:// links and cross-reference them against the active manifest. This flags any archived skills that are mistakenly referenced in routing tables or documentation.

Automated YAML validity checks focus on syntax, routing table corruption, and directory-manifest consistency, but may not catch semantic logic errors. They verify that referenced skills exist and identify naming typos, yet require a properly structured skill repository to function correctly.