ads-validate picks the narrowest validation target and runs it: a contract or bundle through the deterministic core validator, scores, a run’s manifest and source lineage, a capability, the whole repository, or a release through a fresh-context verifier.
Results come back as machine-readable pass or fail with the highest-priority blocker, exact evidence and recovery steps. It also covers install and uninstall safety, allowing removal only of paths listed in the ownership manifest and rejecting pipe-to-shell install instructions.
What You Get
- A pass or fail result in machine-readable form for the chosen target
- The highest-priority blocker with exact evidence
- Recovery steps
- A failed current-evidence check when an expired claim cannot be reverified
- An install and uninstall safety verdict
Common Use Cases
- Checking a run bundle before rendering a report
- Verifying that a platform capability has tests and sources behind it
- Confirming an uninstall will only remove files the toolkit owns
- Running release readiness gates before tagging a version
What Makes It Unique
Stale evidence and skipped remote CI demote readiness. An uninstall may remove only exact paths in the matching ownership manifest, the whole manifest is validated before any deletion, and an ads-* glob is never used, so an unrelated skill such as ads-weather stays untouched. Pipe-to-shell install instructions are rejected, and archives need a SHA-256 checksum verified against a trusted release channel.
Under The Hood
The skill is written instructions with no scripts of its own. The agent calls the Claude Ads core validator and repository gates, which run commands on your machine, and dispatches a fresh-context verifier subagent for releases. It reads manifests and run files and can check install and uninstall paths, and it stops before any deletion if the ownership manifest is absent, invalid, mismatched or unsafe. Expired claims are handed to ads-research for reverify-or-demote.