The problem
Demos rot
- You rename a flag.
- You change the output.
- You ship a new screen.
The GIF never notices.
Open-source Agent Skill · installs in one line
Your README demo that never goes stale.
Install /evergif in any coding agent. It records a terminal or web demo, embeds it in your README, and CI re-renders it only when what it shows actually changed.
npx skills add https://github.com/ShreyasDasari/evergif --skill evergifdemo/evergif.gif
The fix
/evergif notices
CI re-runs the exact commands the demo shows and hashes the output.
Match means nothing renders. Change means a fresh GIF lands on your branch.
How it works
Three steps, no ceremony
1
Ask your agent
“Add a demo gif to my README.” It inspects the project and picks what’s worth showing.
2
It records and embeds
A committed vhs tape or Playwright script, an optimized GIF, and an embed block in your README.
3
CI keeps it honest
Output-hash freshness re-renders only the demos that actually changed.
See it work
Show, don't claim
The same skill, three ways: a terminal recording, a web app recording, and the CI check that keeps both honest.
You
add a demo gif to my README
/evergif
Inspected the repo — a Python CLI with 3 commands. Recording --help, list --open, and stats. Writing demo/evergif.tape…
demo/evergif.gif
What it wrote into your README
<!-- evergif:start -->
<!-- evergif:end -->evergif --web --url http://localhost:3000 --serve "npm run dev" \
--steps "goto /; wait #invoice; pause 800; click text=Create invoice"/evergif starts your dev server, waits for the port, records the flow with Playwright, stops the server, and converts the video to an optimized GIF.
localhost:3000
Push to main
Re-run the demo's commands, hash the output
matches demo/evergif.lock?
Match
Nothing renders. Your GIF is still true.
Changed
Re-render, commit the new GIF to your branch.
Output hashing, not pixel diffing — terminal recordings jitter by a frame, so pixel diffs would churn every week. Command output changes only when your CLI does.
What lands in your repo
Four files, all reviewable
your-project/
- demo/evergif.tape# the recording script, committed so renders are reproducible
- demo/evergif.gif# under 2 MB where possible, never over 5 MB
- demo/evergif.lock# what the demo showed, for the CI freshness check
- README.md# an embed between <!-- evergif:start --> / <!-- evergif:end -->
Works with your agent
One skill, every agent
- Claude Code
- Gemini CLI
- Codex CLI
- GitHub Copilot
- Cursor
- OpenCode
- Windsurf
- Cline
- Goose
- Amp
- Antigravity
One canonical skill, symlinked to every agent's discovery path.
Logos are the property of their respective owners and do not imply endorsement.
Features
Built like a CLI tool, not a SaaS
Terminal and web
vhs for CLIs and TUIs, Playwright for web apps.
Only re-renders what changed
Output hashing, not pixel diffing, so demos don’t churn weekly.
Safe by construction
Refuses destructive, networked, or credential-exposing commands in code, not just in the prompt.
Legible by default
Recorded at 1100px display width, never downscaled, colors given up last.
No local toolchain needed
CI renders tapes for contributors who have nothing installed.
Several demos per README
Each with its own marker block and lock file.
Record it once. Let CI keep it true.
Add /evergif to your project and never ship a stale demo again.
npx skills add https://github.com/ShreyasDasari/evergif --skill evergif