Validate artifact
Skill All-The-Vibes/ATV-PaperBoard/adapters/copilot-cli/_dist/skills/validate-artifact
Run ENFORCE checks on a rendered artifact slug: Google design.md lint + HTML-side color-token trace. Reports ACCEPT or FAIL with fail_class. Invokes `paperboard validate`.From its SKILL.md
npx -y skills add All-The-Vibes/ATV-PaperBoard --skill validate-artifactAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 1 command, including `paperboard validate <slug>`.
SKILL.md
1.0 KB, 192 tokens by cl100k_base, as published. Nobody here has run it
validate-artifact
Enforces design contract compliance on a previously rendered artifact.
Usage
paperboard validate <slug>
When to invoke
- After
render-artifactcompletes, to confirm the artifact is compliant. - When the
artifact-revieweragent requests validation. - Before publishing or persisting an artifact as final.
Checks performed
- lint —
@google/design.mdJSON lint on the paired DESIGN.md sidecar. - color-trace — Every inline hex color in the HTML must appear in the DESIGN.md Colors section.
Output
Prints one of:
✓ ACCEPT slug=<slug>— all checks passed; exit 0.✗ FAIL(<fail_class>) slug=<slug>— details follow; exit 1.
fail_class is one of: none | lint | color-trace | environment
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most quality gates skills give in 192 tokens
Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06
- Read full output and check exit codein 45 of 1524, across 40 files
- Verify output confirms the claimin 44 of 1524, across 39 files
- Identify the command that proves the claimin 43 of 1524, across 39 files
- Execute the full verification commandin 36 of 1524, across 30 files
- Produce a verification reportin 34 of 1524, across 18 files
- Review git diff changesin 30 of 1524, across 16 files
- Fix build failures immediatelyin 29 of 1524, across 9 files
- Group findings by severityin 28 of 1524
- State claim only with evidencein 27 of 1524, across 22 files
- Verify regression tests with red-green cyclein 26 of 1524, across 22 files
- Run the full test suitein 26 of 1524, across 25 files
- Run test suite with coveragein 25 of 1524, across 10 files
Said here and by no other author read
- run paperboard validate on the artifact slug
- verify all inline hex colors exist in design documentation
- lint the paired design sidecar file
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.