agentleFS
imMamdouhaboammarimMamdouhaboammar/linkedin-animated-infographics/skills/render-gif/SKILL.md

render-gif

Skill14 starsChanged 3 months agoMITView on GitHub

Render an existing infographic artboard HTML to a deterministic looping GIF, then report motion, seam, and file-size evidence without changing the approved design.

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. Distinctive:

    Use when the user already has artboard HTML and wants the GIF output, wants a render rerun after a targeted fix, or needs the three core …

    line 20
  2. Very specific:

    If no path is supplied, locate candidate build/*.html artifacts and ask/select rather than guessing.

    line 34
  3. Very specific:

    If duration/fps are not supplied, use a verified timing row from the motion skill.

    line 41

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

/linkedin-animated-infographics:render-gif

Arguments: $ARGUMENTS

Purpose

Provide a focused workflow for rendering an already approved artboard. This workflow does not redesign copy, layout, palette, or motion direction; it turns the existing artifact into deterministic GIF evidence.

Read helper/GUIDE.md first.

Use when

Use when the user already has artboard HTML and wants the GIF output, wants a render rerun after a targeted fix, or needs the three core render measurements without running the entire new-post workflow.

Inputs

  • path to approved artboard HTML
  • optional duration/fps override
  • desired output path and file-size budget

Outputs

Return the rendered GIF plus motion percentage/verdict, seam result, file size, and any HOLD that prevents a trustworthy render.

Procedure

  1. If no path is supplied, locate candidate build/*.html artifacts and ask/select rather than guessing.
  2. Lint before rendering:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/lint_artboard.sh <path>
  1. If duration/fps are not supplied, use a verified timing row from the motion skill. Do not invent arbitrary timings that cannot close cleanly.
  2. Render:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/render.sh <path> <out.gif> --duration <d> --fps <f>
  1. Inspect motion:, seam, and file size. If the seam fails, use the motion debugging reference to identify the likely cause instead of guessing.
  2. Return the GIF and concise render evidence. Do not add a design postamble that implies unperformed QA.

HOLD conditions

Return a HOLD when lint fails, browser capture is unavailable, frame 0 is invalid, the loop seam fails, output exceeds the accepted budget after controlled fallback, or the render evidence cannot be produced reliably.

Related components

  • routing authority: helper/GUIDE.md
  • domain render skill: skills/render/SKILL.md
  • motion skill: skills/motion/SKILL.md
  • render worker: agents/render-qa.md
  • full QA workflow: skills/qa-post/SKILL.md

Research gates

bounded-verification applies to render failure/re-check behavior. The workflow reports evidence and does not silently mutate the artifact to force a PASS.

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.