bad--name

To validate skill metadata for naming convention issues, you can use automated discovery pipelines to identify skills with consecutive hyphens in their names, ensuring strict adherence to naming rules for reliable operation.

When a skill name contains consecutive hyphens, it indicates a potential naming convention issue that can cause parsing errors during agentic skill discovery and validation processes, requiring flagging for correction.

To check if your system handles special characters in skill names, run an illustrative test skill with double hyphens through your validation pipeline to verify parsing behavior and identify metadata handling limitations.

Skill discovery fails with unconventional naming formats because consecutive hyphens and special characters violate strict naming rules, disrupting parsing logic and preventing reliable metadata validation during automated processing.

No, you do not need external dependencies to run naming convention checks on skill metadata, as the identification and flagging of consecutive hyphens operates independently within standard agentic validation pipelines.

No, you cannot use this naming convention check for operational tasks, as it serves an illustrative and demonstrative purpose for testing how systems handle unconventional names rather than executing direct user-facing commands.