← ClaudeAtlas

okhp3-artifact-validationlisted

Validate a project change, draft, research packet, skill, promotion package, or handoff before it is treated as complete. Use after meaningful work and before handoff, graduation, publication review, or reliance on an artifact. Run the identified project validator when one exists, then add judgment checks the script cannot prove.
OKHP3/skillz · ★ 2 · AI & Automation · score 68
Install: claude install-skill OKHP3/skillz
# okhp3-artifact-validation **OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3) ## Output contract Return the artifact path and scope, checks run, status for each check, evidence, blockers, warnings, checks not run, and the next action. A missing validator is `NOT RUN` or `BLOCKED`, never `PASS`. Keep validation read-only unless a separate repair request authorizes a specific change. Choose checks proportionate to the artifact and consequence. ## Mechanical floor For project-wide or structural work, first identify the project-declared validator and confirm that it exists. Run it from the project root or the location its own instructions require. Do not assume a particular filename, operating system command, or repository layout. For a skill, also run the host's available skill validator when one is available and confirm its description matches its actual trigger boundary. For code or generated files, run the targeted parser, test, linter, build, or render check appropriate to that format. ## Judgment checks Confirm: - the real path and changed scope; - unrelated owner work remains intact; - factual claims and citations are supportable; - evidence tiers are visible where they affect future decisions; - no secret, confidential, employer, client, or accidental generated material entered scope; - links, names, metadata, and referenced resources exist; - the artifact satisfies the current request rather tha