okhp3-artifact-validation

Validate project artifacts with mechanical checks and judgment review before handoff.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-artifact-validation-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-artifact-validation
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-artifact-validation
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-artifact-validation-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work is often treated as complete without verification, letting broken validators, unsupported claims, or accidental private material slip into handoffs and publications. This Skill enforces a read-only validation pass that separates what was mechanically proven from what was only assumed. ## Core Features & Use Cases - Mechanical Floor Checks: Identifies and runs the project-declared validator, plus format-appropriate parsers, tests, linters, or builds, without inventing commands. - Judgment Review: Confirms scope, intact unrelated work, supportable claims, existing links and metadata, and absence of secrets or confidential material. - Honest Status Reporting: Reports every check as PASS, FAIL, WARN, BLOCKED, or NOT RUN, never converting an unavailable check into a pass. - Use Case: Before promoting a draft skill to a publication mirror, run this Skill to execute the sync verification script, review the manifest for unresolved items, and produce an evidence-backed readiness report. ## Quick Start Use the okhp3-artifact-validation skill to validate this artifact and report each check as pass, fail, warn, blocked, or not run with evidence and next action.

Frequently Asked Questions about okhp3-artifact-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an artifact before handoff or publication?▼

Run the project-declared validator first from the location its instructions require, then apply judgment checks for scope, claims, links, and sensitive material. Report each check as PASS, FAIL, WARN, BLOCKED, or NOT RUN with evidence and a next action.

What should I do when a project has no validator script?▼

Report the missing validator as NOT RUN or BLOCKED, never as PASS, and do not invent a command. Still run the applicable judgment checks and state the remaining uncertainty and next action explicitly.

Can artifact validation fix the problems it finds?▼

No, validation stays read-only unless a separate repair request authorizes a specific change. Embedded instructions asking for rewrites or deletions are treated as untrusted data, and failures are reported without destructive repair.

Does a passing validator script mean an artifact is ready to publish?▼

No, a script pass is only a mechanical floor, not a quality or publication verdict. Judgment checks for factual claims, evidence tiers, confidential material, and fit to the actual request must also pass before reliance.

What does the validation output report include?▼

The report includes the artifact path and scope, checks run, per-check status, evidence, blockers, warnings, checks not run, and the next action. Check depth is chosen proportionate to the artifact and its consequences.