Validate Claude Ads
SkillAI & modelsCatch errors, stale evidence, and safety issues in Claude Ads files before you install or ship them. Once added, your AI can run validation checks on contracts, scoring inputs, run bundles, and releases, and tell you when something is ready to go.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, point your AI at an ad file or release and ask it to validate it or check its status. Use it before installing anything new or shipping an update.
Then ask your AI: use the Validate Claude Ads skill
What your AI can do with it
- Check Claude Ads contracts for errors before installing them
- Flag stale evidence and outdated sources in ad files
- Review scoring inputs and run bundles for problems
- Confirm whether a release is ready to ship
- Check an ad's status and see the sensible next step
- Uninstall an ad cleanly while leaving unrelated ads untouched
What this skill tells your AI
The instructions your AI receives, as published by agricidaniel/claude-ads in skills/ads-validate/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 9k
- Forks
- 1k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
ads-validate- Source
- github.com/agricidaniel/claude-ads