skill-qa-harness

To validate Codex skills across a repository, you can use a QA harness to inventory skills in .agents/skills, enforce frontmatter requirements like name and description, and detect optional components such as scripts and references.

Inventorying and testing skills in .agents/skills requires a centralized QA harness that scans the directory, validates structure and frontmatter, and triggers repository quality gates before executing checks.

Yes, you can run repository quality gates including lint, test, and build operations before executing skill checks to ensure overall repository stability and prevent integration errors.

Validating skills enforces strict frontmatter requirements ensuring both the name and description fields are present, while also detecting optional components like scripts, references, and assets to support operations.

Yes, the QA harness detects optional components such as scripts, references, and assets during the skill validation process to support ongoing operations and maintain a comprehensive catalog.

Checking for duplicate names when managing skills prevents integration errors and maintains quality across implementations by ensuring each skill has a unique identifier within the repository catalog.