agentleFS
All-The-VibesAll-The-Vibes/ATV-PaperBoard/skills/validate-artifact/SKILL.md

validate-artifact

Skill1 starsChanged 6 months agoApache-2.0View on GitHub

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`.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After render-artifact completes, to confirm the artifact is compliant.

    line 20
  2. Very specific:

    When the artifact-reviewer agent requests validation.

    line 21
  3. Distinctive:

    Before publishing or persisting an artifact as final.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

validate-artifact

Enforces design contract compliance on a previously rendered artifact.

Usage

paperboard validate <slug>

When to invoke

  • After render-artifact completes, to confirm the artifact is compliant.
  • When the artifact-reviewer agent requests validation.
  • Before publishing or persisting an artifact as final.

Checks performed

  1. lint — @google/design.md JSON lint on the paired DESIGN.md sidecar.
  2. 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.