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

regenerate-artifact

Skill1 starsChanged 6 months agoApache-2.0View on GitHub

3-step differentiated retry for a failing artifact slug: switch tier, drop optional components, fall back to default design. Invokes `paperboard regenerate`.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never invoke without a prior validation failure — check first.

    line 21

≈ “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

regenerate-artifact

Recovers a failing artifact via three progressively conservative retry steps.

Usage

paperboard regenerate <slug>

When to invoke

  • validate-artifact returns FAIL and the artifact-reviewer recommends REGENERATE_VIA regenerate-artifact.
  • Never invoke without a prior validation failure — check first.

Retry strategy

StepChangeRationale
1Switch tier (cycle among atv / pico / daisy; atv is default)Different tier/CSS framework may avoid inline color conflicts
2Drop optional components from inputReduces surface area for color violations
3Fall back to paperboard.DESIGN.mdKnown-good default design always lints clean

Output

Prints: Regenerate step=<N> new_slug=<slug> status=ACCEPT|FAIL(<fail_class>)

Exit 0 on ACCEPT, exit 1 if all three steps fail.

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.