different-name

To validate skill metadata naming conventions, you identify and flag skills where the `name` field in `SKILL.md` does not match the directory name. This ensures organizational consistency and prevents discovery issues in agentic systems.

When a skill name does not match its directory name, it creates a directory mismatch that highlights potential configuration issues. This inconsistency can cause discovery issues within agentic systems that rely on accurate file structure alignment.

Skill configuration fails discovery in agentic systems when the `name` field in `SKILL.md` differs from its file system location. Validating naming conventions resolves this directory mismatch and restores proper organizational consistency.

Yes, you can use a naming convention validation skill for testing systems that rely on consistent naming conventions. It demonstrates how a skill's metadata can differ from its directory and helps flag configuration issues.

The best way to check SKILL.md metadata against its file system location is to scan for directory mismatches. This identifies where the defined `name` field does not align with the directory name, ensuring structural consistency.

A limitation of using a demonstration skill for directory mismatch testing is that it serves demonstration purposes only and does not provide a direct user-facing quick start command for automated or continuous validation.