invalid-agent-skill

To validate agent configs, you apply a parser that inspects agent types and naming rules to reject underscores and enforce kebab-case. This flags invalid definitions for remediation before runtime.

Allowed agent naming conventions include built-in types like Explore and Plan, or custom names that strictly use kebab-case. The validation rejects any agent names containing underscores.

Yes, you can integrate agent config validation into CI pipelines to catch invalid agent definitions during pull requests. It acts as a pre-merge check to prevent runtime errors from incorrect types.

Agent config validation fails because the rules reject underscores and enforce kebab-case for custom names. You must rename the agent using hyphens instead of underscores to pass validation.

The best way to check for invalid agent types is to run a validation pipeline that inspects definitions against allowed types. This process flags invalid types for remediation before deployment.