duplicate-name

To detect duplicate skill names in a repository, run a validator that checks YAML frontmatter across tests and fixtures. It reports name collisions, ensuring each skill unit maintains a unique name for reliable discovery.

Skill name validation fails during repository-wide testing when multiple fixtures share identical names in their YAML frontmatter. The validator detects these name collisions across the skills registry and provides a clear error to guide remediation.

The best way to prevent name collisions in a skills registry is to validate YAML frontmatter structure during development. This ensures every skill definition has a unique name across the repository, avoiding ambiguous references during discovery.

Yes, you can validate YAML frontmatter structure to ensure unique skill names across fixtures. The validator specifically checks the name and description fields within the frontmatter to detect and report any conflicting skill names.

You need to run a duplicate name check across your skills registry during repository-wide validation. This is especially necessary when adding new fixtures or tests to prevent name collisions that create ambiguous references during skill discovery.