ss-validate-skills

Skill validation involves parsing SKILL.md frontmatter, checking naming conventions, and verifying structural rules to ensure repository compliance. This process identifies metadata errors and structural inconsistencies before code merges.

Run skill validation during pre-release checks and within GitHub Actions CI pipelines. It acts as a merge gatekeeper, catching frontmatter and structural issues early to prevent broken builds and unexpected runtime behavior.

Yes, skill validation integrates into GitHub Actions workflows to provide continuous validation. It automatically checks SKILL.md frontmatter and structural rules during CI pipelines, preventing non-compliant skills from merging.

The best way to audit skill files before merging is to run an automated validation script that checks SKILL.md frontmatter correctness, naming conventions, and structural integrity, confirming all project requirements are met.

Yes, verifying skill metadata requires glob, grep, and read tools to discover and parse SKILL.md files. These tools locate skill definitions, extract frontmatter, and verify structural rules across the repository.

Skill validation fails on incorrect frontmatter because it strictly checks for compliance with established standards. Parsing errors or missing metadata fields prevent the skill from passing pre-release audits and CI pipeline gates.