test-secondary-skill

To validate secondary skill deployment in a CI pipeline, check that each skill has a root SKILL.md with valid YAML frontmatter containing name and description, and verify its directory is placed correctly under the secondary_skills path to ensure it remains hidden from the main catalog.

A secondary skill is a capability isolated under the secondary_skills directory to keep it hidden from the primary skills catalog. You need to validate its deployment during CI validation, deployment audits, or manual verifications when adding, updating, or removing these skills across environments.

Yes, secondary skill validation requires a root SKILL.md file containing valid YAML frontmatter. The frontmatter must explicitly include the name and description fields to pass metadata integrity checks and confirm proper deployment structure.

To ensure secondary skills remain hidden from the main skills view, verify they are placed correctly within the dedicated secondary_skills directory. This isolation prevents them from appearing in the primary skills catalog during deployment audits.

The best way to audit skill directory structure and metadata integrity is to enforce that each skill has a root SKILL.md with valid YAML frontmatter, checking directory placement under the secondary_skills path and confirming required name and description fields are present.