correct-name

To validate skill metadata consistency, run a check that compares the slug in skill.meta.json against the YAML frontmatter name in SKILL.md. This detects mismatches early, preventing broken skill discovery and installation behavior in your registry.

Your skill registry fails discovery when the slug in skill.meta.json does not match the YAML frontmatter name in SKILL.md. Running a metadata consistency check surfaces an actionable validation error to fix this exact mismatch.

Yes, you can use metadata validation in CI testing for skill packaging. It applies to CI or local testing environments to enforce alignment requirements and catch naming inconsistencies before skills are published to a registry.

To test for slug and name mismatches, validate your skill directory against a known invalid fixture case. This fixture-driven approach reliably reproduces and verifies the error condition during local testing or CI pipeline execution.

When a declared slug does not match its frontmatter name, the validation process surfaces an actionable validation error. This enforces strict identifier alignment for atom-like units and prevents inconsistent metadata fields from breaking registration.

Yes, you need to fix metadata mismatches before refactoring skill identifiers. Validating strict identifier alignment ensures that both the human-facing name in SKILL.md and the slug in skill.meta.json remain synchronized during registry updates.