audit-skill

Auditing a skillset for compliance involves checking primitives, MCP configurations, and workflow artifacts against safety requirements. This process identifies structural gaps and generates an AUDIT_REPORT.md with structured findings and suggested fixes.

A skillset audit is a qualitative validation of primitives and safety that ensures a submitted skillset adheres to structural requirements. You need it when submitting to skillsets.cc or verifying interoperability against a reference repository in production.

Validating skillset interoperability requires auditing your submitted skillset against a reference repository. The audit checks primitives, scans, and workflow artifacts, then outputs an AUDIT_REPORT.md and INSTALL_NOTES.md to confirm compliance.

Yes, you can generate an audit report by running validation against your manifest, CLAUDE.md, QUICKSTART.md, and CRITERIA.md files. The process produces an AUDIT_REPORT.md with findings and an INSTALL_NOTES.md with runtime dependency summaries.

Yes, the skillset audit works without external dependencies. It runs directly against your local content files, including the manifest and documentation, to produce structured findings and installation notes for your repository.

Your skillset fails the production readiness check when the audit identifies gaps in primitives, safety scans, or workflow artifacts. The generated AUDIT_REPORT.md provides specific findings and suggested fixes to address documentation and compliance issues.