gif-loop
Skill0 starsChanged 14 days agoMITView on GitHub
Make a short, seamless, looping GIF (4 to 10 s) for a README, docs page, release note or social post - a product moment, a dashboard coming alive, a process diagram, a launch title - built as a deterministic HTML page and encoded to fit a size budget. Use when the user asks for a GIF, an animated preview, a hero animation for a README, or to turn part of a claude-veo video into a GIF.
In this repository3 other files it gives its agents.
- product-demoSkill
- video-briefSkill
- video-engineSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Look at two or three frames of the GIF itself (ffmpeg -i preview.gif -vf "select='eq(n\,60)'" -frames:v 1 f.png): banding, dithering noise …
≈ “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.
Files
Looping GIF
Uses the engine in ../video-engine/ (kit and scripts). Read ../video-engine/SKILL.md first. Working examples: examples/gifs/ in this repository (dashboard, HTTPS handshake, CI/CD pipeline, launch title).
Design for a loop
- One moment, 6 to 8 s. A GIF shows one idea: numbers counting up, a chart drawing, messages travelling, steps turning green, a title assembling. No storyboard of many scenes.
- Seamless loop: wrap everything in
win(t, 0, DURATION, 0.5)so the frame fades from and back to the bare background; the first and last frames then match. - Readable small: it will be seen at 600 to 800 px wide. Titles 60 px or more and body text 24 px or more in the 1920 design space; few words; strong contrast.
- GIF-friendly colours: flat fills and soft gradients compress well; avoid full-screen noise, photos and long blurred motion. The drifting blobs are fine.
- Same style and motion rules as the videos (
../video-engine/references/style.md).
Make it
E=../video-engine # this skill's sibling folder
node $E/scripts/shots.mjs loop.html sheet.jpg 1 3 5 7 --cols 4 --tile 480 # check
node $E/scripts/gif.mjs --in loop.html --out preview.gif --width 800 --fps 15 --max-mb 3gif.mjs also takes an MP4 (--in demo.mp4 --from 18 --to 25) to cut a GIF from a finished video. It renders the page at twice the GIF width, builds a palette from the clip, and steps the fps and then the width down until the file fits --max-mb.
Check and deliver
Look at two or three frames of the GIF itself (ffmpeg -i preview.gif -vf "select='eq(n\,60)'" -frames:v 1 f.png): banding, dithering noise and unreadable text show only there. Report the size, width and fps. For GitHub READMEs keep each GIF under about 3 MB, or link a poster to the MP4 instead.
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
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.

