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

render

Skill14 starsChanged 3 months agoMITView on GitHub

Capture deterministic infographic frames, assemble GIF output, measure motion/seam/file size, and run the render acceptance gates before shipment.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, publish and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

  • VercelSkill

    publish

    Publish a single demo to v0 and optionally create Typefully drafts. Use when the user says "publish", "publish to v0", or "create typefully draft" for a demo.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 4 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Read helper/GUIDE.md first.

    line 12
  2. Very specific:

    Use when capturing frames, building a GIF, diagnosing blank/jittery/oversized output, measuring seam or changed pixels, running render QA, …

    line 16
  3. Distinctive:

    Use the one-command path when possible:

    line 31
  4. Very specific:

    Read references/qa-gates.md, references/production-pipeline.md, and references/pixel-perfect-browser-inspection.md.

    line 44
  5. Distinctive:

    Treat frame 0 as a complete poster frame.

    line 46
  6. Very specific:

    Keep the outer 48px safe zone free of motion and account for known SVG <defs> false positives when diagnosing geometry.

    line 48
  7. Very specific:

    If encoding exceeds the budget, prefer the existing controlled color/fps/scale fallback rather than arbitrary re-authoring.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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

Render and ship

Purpose

Convert an approved static/animated artboard into deterministic render evidence and final GIF output. Rendering is an acceptance stage, not a place to redesign the story.

Read helper/GUIDE.md first. Render evidence feeds post-critic and story-verifier through build/render-report.json.

Use when

Use when capturing frames, building a GIF, diagnosing blank/jittery/oversized output, measuring seam or changed pixels, running render QA, or preparing a final LinkedIn image GIF.

Inputs

  • approved build/post.html
  • duration/fps from verified motion timing when animated
  • output file-size budget
  • expected frame-zero state and safe-zone constraints

Outputs

Return GIF/static render output plus build/render-report.json containing frame-zero, mobile legibility, motion percentage, seam result, duration/fps, file size, and any blocking render finding.

Procedure

  1. Use the one-command path when possible:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/render.sh build/post.html build/post.gif --duration 6.0 --fps 12.5
  1. The underlying deterministic stages are:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/capture_frames.py build/post.html --out build/frames --duration 6.0 --fps 12.5 --selector "#artboard"
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/build_gif.py build/frames --out build/post.gif --fps 12.5 --max-mb 5 --colors 128
  1. Read references/qa-gates.md, references/production-pipeline.md, and references/pixel-perfect-browser-inspection.md.
  2. Inspect three core measurements: mean changed-pixel motion:, loop seam relative to normal frame deltas, and file size.
  3. Treat frame 0 as a complete poster frame. It must remain readable before autoplay.
  4. Inspect the 350px feed downscale honestly. Render success without feed-scale legibility is not acceptance.
  5. Keep the outer 48px safe zone free of motion and account for known SVG <defs> false positives when diagnosing geometry.
  6. If encoding exceeds the budget, prefer the existing controlled color/fps/scale fallback rather than arbitrary re-authoring.
  7. For publishing guidance, read references/publishing-playbook.md: LinkedIn GIF output is uploaded as an image; links normally belong in the first comment when the post strategy calls for them.

HOLD conditions

Return a HOLD when capture fails, frame 0 is incomplete, the seam does not close, changed-pixel motion indicates unintended full-canvas animation, feed-scale output is unreadable, safe-zone rules fail, or output cannot fit the accepted file budget without unacceptable degradation.

Related components

  • routing authority: helper/GUIDE.md
  • focused render workflow: skills/render-gif/SKILL.md
  • motion skill: skills/motion/SKILL.md
  • QA gates: references/qa-gates.md and references/pixel-perfect-browser-inspection.md
  • production setup: references/production-pipeline.md
  • render worker: agents/render-qa.md
  • independent verifier: agents/story-verifier.md

Research gates

bounded-verification governs how render failures enter the repair/re-check loop. contrast-discipline remains relevant to rendered evidence, and evidence-traceability applies when the final artifact contains factual proof that must be checked visually.

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.