package-auditor

To audit a skill package for release-readiness, run the validation check against your package directory. The auditor inspects frontmatter, resolves pointers, checks eval schemas, and examines release evidence to identify any structural issues or verification gaps that could block your release.

Release-blocking structural issues include missing or invalid frontmatter, broken resolved pointers, incorrect eval schemas, and missing release evidence. The package auditor separates these blocking failures from general improvements to provide actionable feedback on what must be fixed.

You need to validate package structure before promoting a skill package to a higher environment. Running an audit early catches potential release issues related to frontmatter, pointers, and eval schemas, ensuring the integrity and quality of your installable skill packages.

Yes, you can check eval schemas and frontmatter without external dependencies. The package auditor operates independently to inspect package structure, resolve pointers, and examine release evidence, requiring no additional modules to complete its validation workflow.

The package auditor reports blocking failures separately from improvement suggestions. Blocking failures indicate critical structural issues in frontmatter, pointers, eval schemas, or release evidence that must be resolved, while improvements highlight non-critical verification gaps for better quality.