loop-cover — Claude Code skill: what it does, how to install
Converts newsletter and blog covers into looping 896x640 GIFs across 180 frames. It animates a single chosen detail while keeping the loop jump-free.
npx skills add charlie947/motion-graphics-skills --skill loop-cover -a claude-codeWhat loop-cover does
The skill accepts a 7:5 still PNG or an HTML cover layout. It animates exactly one designated element: a light beam, a drawing stroke, or a soft pulse. The rest of the scene remains locked in place because the skill isolates the element with a code mask instead of relying on video generation models.
Each loop spans 9 seconds at 20 frames per second. The skill offsets the loop so frame 1 presents the fully drawn image. Link previews and email readers display the first frame as a still, so an empty canvas would ruin the card. Frames are encoded in ffmpeg with dither=none to avoid grain flicker on flat background colors.
Before running, the skill checks for brand.md and MOTION.md or asks for fonts and palette hex codes. You will need ffmpeg and python3 installed locally. Without them, the agent cannot run the measurement script that evaluates loop seam differences and frame excursion.
What it helps with
- create a jump-free looping GIF cover for newsletters or blog posts
- place the finished artwork on frame 1 for static link previews
- measure frame excursion and loop seam differences with python3
- prevent flat color banding flicker by turning off dithering in ffmpeg
Example prompts for the agent
- Make a looping GIF cover from cover.png, animate only the orange line drawing itself
- Animate cover.html with a slow pulse on the lighthouse beam for 180 frames
How to install loop-cover
1Skills CLI (Vercel)
npx skills add charlie947/motion-graphics-skills --skill loop-cover -a claude-code2Manually: put the files in place
~/.claude/skills/loop-cover/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/loop-cover/
1Skills CLI (Vercel)
npx skills add charlie947/motion-graphics-skills --skill loop-cover -a codex2Manually: put the files in place
.agents/skills/loop-cover/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add charlie947/motion-graphics-skills --skill loop-cover -a cursor2Manually: put the files in place
.cursor/skills/loop-cover/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install charlie947/motion-graphics-skills loop-cover2Manually: put the files in place
.github/skills/loop-cover/SKILL.md1Skills CLI (Vercel)
npx skills add charlie947/motion-graphics-skills --skill loop-cover -a gemini-cli2Platform CLI
gemini skills install https://github.com/charlie947/motion-graphics-skills --path skills/loop-coverManually: put the files in place
.devin/skills/loop-cover/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add charlie947/motion-graphics-skills --skill loop-cover -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about loop-cover
How to install loop-cover in Claude Code?
Run npx skills add charlie947/motion-graphics-skills --skill loop-cover -a claude-code in your terminal. This downloads the skill directly into ~/.claude/skills/loop-cover/SKILL.md.
What does loop-cover do?
It creates an 896x640 animated GIF from a static image or HTML canvas. It isolates a single graphic element and cycles it over 180 frames without visible jumps.
Why does loop-cover put the completed artwork on frame 1?
Many email clients and social preview scrapers display the very first frame without playing the GIF. Placing the finished drawing on frame 1 guarantees that readers see a complete cover even when autoplay fails.
Source text
SKILL.md · MIT
---
name: loop-cover
description: Turn a newsletter or blog cover into a seamless looping GIF at 896 x 640, 180 frames at 20fps. Only the one element you name moves, the loop is rotated so frame 1 shows the finished picture, and the seam is measured, not eyeballed. Use when someone says "animated cover", "make my cover move", "looping GIF cover", "newsletter cover GIF", "animate my thumbnail" or wants a cover that moves in the inbox without looking busy.
---
# Looping cover GIF
A cover that moves gets noticed in a feed full of stills. It only works if the move is small, the loop never jumps and the first frame still makes sense on its own.
**Before you start:** read `brand.md` and `MOTION.md` if they exist. If not, run `brand-intake` first, or ask for hex codes, a font and a logo file. Never call a result on-brand without them.
## Step 1: Ask for three things, then wait
1. **The cover.** A finished still (PNG) or a cover built in HTML. 896 x 640, or a larger image with the same 7:5 shape.
2. **The one element that moves,** named plainly. "The lighthouse beam." "The orange line drawing itself." "The lines between the cells."
3. **How it moves.** A pulse, a draw-on, a slow drift or a glow. One move, not three.
## Step 2: Build it
**If the cover is HTML:** animate only the named element as a pure function of time, add `window.seek(seconds)`, and capture 180 frames at 20fps (9 seconds).
**If the cover is an image:** animate the still in code. Make a mask of the named element by colour (for example every pixel where blue is much stronger than red), soften its edge a few pixels, and change only those pixels, frame by frame. Nothing outside the mask moves.
For both, use one clean sine cycle or one draw-on, hold and fade across the 9 seconds, so the last frame flows into the first.
**Rotate the loop so frame 1 is the finished picture.** Inboxes and link previews show frame 1 as a still. Frame i draws the moment `((i + offset) mod 180) / 20` seconds, where `offset` puts the fully drawn state first.
Encode with no dithering, because dither adds flicker to every frame of a flat image:
```
ffmpeg -y -framerate 20 -i f%03d.png -filter_complex "split[x][y];[x]palettegen=max_colors=128:stats_mode=full[p];[y][p]paletteuse=dither=none" -loop 0 cover.gif
```
## Step 3: Measure it
```
ffmpeg -v error -y -i cover.gif -vf scale=216:154,format=gray -f rawvideo frames.raw
python3 -c "
n = 216 * 154
d = open('frames.raw', 'rb').read()
f = [d[i:i + n] for i in range(0, len(d), n)]
diff = lambda a, b: sum(abs(x - y) for x, y in zip(a, b)) / n
print('frames', len(f))
print('seam', round(diff(f[-1], f[0]), 2))
print('excursion', round(max(diff(x, f[0]) for x in f), 2))
"
```
Targets from covers I shipped: 180 frames, a seam of 0.0 to 0.3, an excursion of about 0.7 to 2.8, and a file between 0.6 and 2.3 MB. An excursion near zero means nothing visible moves.
## What I learned the hard way
- **"You changed the image entirely."** My first GIF swept a band across the whole frame. Animate only the thing that was named.
- **A video model adds a camera move.** Told "camera holds completely still", it still pushed in. Animating the still in code is the only way to lock the camera.
- **Never measure motion at the halfway frame.** A sine is back at zero there, so a working animation reports no motion. Measure the biggest change against frame 0.
- **In ffmpeg's `eq` filter, add `eval=frame`,** or the expression runs once and nothing moves.
- **Shrink it to 240px wide and look again.** That is the size in an inbox. If the moving element disappears, it is too small.
- **Upload the GIF itself.** Some upload tools convert to PNG and the animation is silently gone. Check the uploaded link still ends in `.gif`.
© charlie947 · MIT · charlie947/motion-graphics-skills