vhs-video
Skill9 starsChanged 4 months agoMITView on GitHub
VHS tape syntax and ffmpeg video handling in readme2demo — how the demo video is generated, the hard-won gotchas, and the duration gate. Use when touching templates/demo.tape.j2, render.py, distill.tape_from_guide, or when a video is short, blank, mis-paced, or fails to render.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- add-engineSkill
- add-failure-classSkill
- debug-runSkill
- docker-sandboxSkill
- git-github-operatorSkill
- python-standardsSkill
- sandbox-toolchainsSkill
The file
Files
VHS tapes & video
The demo video is built from the FINAL step_by_step.md (render stage, after
tutorial finalizes the guide) so the video follows the published guide
step-for-step. distill.tape_from_guide parses the guide's fenced bash blocks
into TapeCommands; templates/demo.tape.j2 renders the tape; render.py
runs VHS in the base image.
Non-negotiable tape rules (each is a scar)
- Never use
Wait+Screenon output text. It matches only the VISIBLE buffer; any pattern in longer-than-one-screen output scrolls off and times the render out. Pace withWait(blocks until the shell prompt returns, so the command — build included — has finished) then a shortSleepto read. - VHS string literals have NO backslash escapes.
vhs_quotepicks a delimiter the text doesn't contain:"→`→'. A string with all three can't be typed (rare; that step is skipped). Typeis single-line. Multi-line commands (heredocs) are typed LINE-BY-LINE viaTapeCommand.lines(Type/Enter per line) so file creation plays on camera — a real shell reads a heredoc until its terminator.- Framerate 24,
Output demo.mp4only. A GIF per-frame render of a multi-minute tape once filled the Docker VM disk.demo.gifis a short downscaled ffmpeg preview cut from the mp4 afterwards (best-effort, never gates the stage). - Hidden preamble
cd /work && clearso the guide's owngit clone ... .starts from the empty workspace.
Duration gate (render.validate_outputs)
expected_min_duration_s sums the tape's Sleeps + typing time; real command
execution (the Waits) only adds on top. A video shorter than ~0.8× that bound
means steps didn't play (stale image, aborted tape) → HARD error, never a
silently short clip. Bounds: 5s..1500s.
Coverage
render writes tape_coverage.json (guide_steps / tape_steps / dropped) and
prints any dropped step. With heredocs now on camera, a dropped step means a
genuinely ungrounded guide command — investigate, don't ignore.
ffmpeg
Used for the gif preview (fps=10,scale=800) and, on the host, ffprobe for
the duration check. Both run inside the base image for the preview; the host
ffprobe check is skipped when ffprobe isn't on PATH.
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.

