Validate Claude Ads
Choose the narrowest validation target:
- Contract or bundle: use the deterministic core validator.
- Scores: validate controls, findings, category weights, and coverage.
- Run: verify manifest completeness, source lineage, privacy, worker status, and
render artifacts.
- Capability: require implementation, fixtures, tests, sources, and truthful mode.
- Repository: run deterministic, routing, security, installer, rendering, evidence,
packaging, and freshness gates.
- Release: dispatch a fresh-context release verifier.
Return machine-readable pass/fail results, the highest-priority blocker, exact
evidence, and recovery steps. Never promote maturity because documentation is
polished or a prior release passed. Stale evidence and skipped remote CI demote
readiness.
If an expired claim cannot be reverified because source or filesystem access is
unavailable, return a failed current-evidence check, demote that claim for the
current run, and block dependent release-current assertions before asking for the
missing access.
Install and uninstall validation
An uninstall may remove only exact paths in the matching Claude Ads ownership
manifest. Validate the entire manifest and configured root boundaries before any
deletion. If the manifest is absent, invalid, mismatched, or unsafe, stop before
deleting anything and require manual review. Never discover targets with an
ads-* glob; unrelated skills such as ads-weather must remain untouched.
Reject pipe-to-shell install instructions. A safe install uses the host's native
installer or a locally inspected checkout/archive; archives require a SHA-256
checksum verified against a trusted release channel before execution.
1---2name: ads-validate3description: Validates Claude Ads contracts, bundles, scores, runs, capabilities, repositories, and releases with deterministic checks and recovery steps.4---56# Validate Claude Ads78Choose the narrowest validation target:910- Contract or bundle: use the deterministic core validator.11- Scores: validate controls, findings, category weights, and coverage.12- Run: verify manifest completeness, source lineage, privacy, worker status, and13 render artifacts.14- Capability: require implementation, fixtures, tests, sources, and truthful mode.15- Repository: run deterministic, routing, security, installer, rendering, evidence,16 packaging, and freshness gates.17- Release: dispatch a fresh-context release verifier.1819Return machine-readable pass/fail results, the highest-priority blocker, exact20evidence, and recovery steps. Never promote maturity because documentation is21polished or a prior release passed. Stale evidence and skipped remote CI demote22readiness.2324If an expired claim cannot be reverified because source or filesystem access is25unavailable, return a failed current-evidence check, demote that claim for the26current run, and block dependent release-current assertions before asking for the27missing access.2829## Install and uninstall validation3031An uninstall may remove only exact paths in the matching Claude Ads ownership32manifest. Validate the entire manifest and configured root boundaries before any33deletion. If the manifest is absent, invalid, mismatched, or unsafe, stop before34deleting anything and require manual review. Never discover targets with an35`ads-*` glob; unrelated skills such as `ads-weather` must remain untouched.3637Reject pipe-to-shell install instructions. A safe install uses the host's native38installer or a locally inspected checkout/archive; archives require a SHA-25639checksum verified against a trusted release channel before execution.
Agrici Daniel