artifact-validator
Validate one or more workflow artifacts (Markdown) against the fixed skeleton and the citation rules. This skill is read-only: it never edits artifacts, it only reports findings so the coordinator can map failures to agents.
What to check
Run every check below against each artifact file. Report each check as
PASS or FAIL with concrete findings (quote the offending lines).
Structure (backs gate G8)
- The file starts with a single
#title line. - **Owner agent:** <agent>is present and matches the artifact ownership table inCLAUDE.md(artifact filename ↔ agent name).- Sections exist, in this order, each as
##:Inputs used,Summary,Details,Costs,Sources,Open issues. ## Costsis either a table (| Item | Unit | Qty | Unit cost | Total | Source / basis |) or the exact sentenceNo costs in this artifact.## Open issuescontains at least one bullet, orNone.## Sourcescontains at least one bullet unless the artifact is explicitly markedNot applicable(then it must state the reason).
Citations (backs gates G7 and G3)
- Every source bullet has the shape
- <Page title> — <URL> (fetched YYYY-MM-DD; supports: <claims>). - URLs are real pages:
https://orhttp://, no placeholders (example.com,localhost,TODO,...), no invented patterns. - Every named venue, caterer, provider, price or weather figure in
Details/Coststraces to a claim in aSourcesbullet. A recommendation without a source is a FAIL. - Prices must come from a source or be marked
price on requestwith the estimate basis stated. Unmarked, unsourced prices are a FAIL.
Ownership and safety
- The artifact does not claim work owned by another agent (e.g. a venue artifact containing a full timeline).
- Nothing in the artifact asks anyone to write
output/event-plan.htmlorapproval.json— those are forbidden outside html-builder / /approve-event.
How to report
Produce a compact report, one line per check:
<artifact> C1 PASS ... C12 PASS
<artifact> C9 FAIL — "Koneser Hall" has no source citation → responsible: venue-planner
End with OVERALL: PASS or OVERALL: FAIL — <responsible agents>.
On FAIL, the coordinator applies the retry policy (see CLAUDE.md §6): re-run only the
responsible agent with these findings, regenerate downstream dependents, re-validate.