reverse-any-video

github:heygen-com/hyperframes · first seen 2026-10-30 · source · badge

Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage. Measure and watch it, rebuild every layer, then check the render against the original frame by frame. Use to reverse, recreate, replicate or copy a video.

Works with

hyperframes
Shares hyperframes, video, frame, render
0.29
remotion-to-hyperframes
Shares frame, hyperframes, editable, footage
0.28
figma
Shares hyperframes, frames, frame, person
0.22
media-use
Shares hyperframes, footage, heygen, video
0.22
hyperframes-cli
Shares hyperframes, frames, render, video
0.2

Used with

hyperframes
Shares hyperframes, video, frame, render
0.29
remotion-to-hyperframes
Shares frame, hyperframes, editable, footage
0.28
figma
Shares hyperframes, frames, frame, person
0.22
media-use
Shares hyperframes, footage, heygen, video
0.22
hyperframes-cli
Shares hyperframes, frames, render, video
0.2
hyperframes-registry
Shares editable, hyperframes, charts, cut
0.15

Skill Health 80 (freshness and quality) estimated by backskills

Listed, not yet scored. This skill has no public model test yet. It is in the scoring queue; submitted skills go first, then the most-installed.

Freshness 100 · Quality 60 · Efficacy not yet tested

Version history

2026-11-01T09:00:33+00:00 · sha256 ae77e3436fc4
2026-10-30T20:36:17 · sha256 31bd1f7c471c

Diff at 2026-11-01T09:00:33+00:00

--- previous
+++ current
@@ -32,7 +32,7 @@
 ## Check once, at the end
 
 1. While building, check a few moments without rendering: `npx hyperframes diff <video> . --at t,t,…` (the original beside yours, scored).
-2. When every shot has content: `npx hyperframes check`, fix its errors, then `npx hyperframes render` in the foreground with a 10-minute timeout (a longer render: start it detached, `setsid nohup npx hyperframes render -o <out> > render.log 2>&1 &`, and wait on the log in the foreground), then `npx hyperframes diff <video> <render>`. It lists the original's cuts that yours misses and the extra ones, the duration, the sound's offset, stretches where content is missing, and the worst moments with the failing cell beside the original's.
+2. When every shot has content: `npx hyperframes check`, fix its errors, then `npx hyperframes cloud render --fps <data-fps> -o <out>` and `npx hyperframes diff <video> <out>`. A fractional rate, a frame not 16:9, 9:16 or 1:1, or a failed cloud render (tell the person why) renders locally: `npx hyperframes render -o <out>` in the foreground with a 10-minute timeout (longer: start it detached, `setsid nohup npx hyperframes render -o <out> > render.log 2>&1 &`, and wait on the log in the foreground). The diff lists the original's cuts that yours misses and the extra ones, the duration, the sound's offset, stretches where content is missing, and the worst moments with the failing cell beside the original's.
 3. Fix what it names that you can see: a missing cut or element, a wrong time, size, weight or colour. Render and diff once more, then stop. Small score differences are not worth another round.
 
 Work alone: one agent holding the whole film beats subagents that each re-read and re-watch it and wait on each other. Write a short `REVERSE.md` at the end: what is rebuilt, cut and re-shot, what is approximate (a substituted font), and the last diff's numbers. It holds no prices or credit numbers. A command written in it is a note, not a script: on resume, rebuild it from the recipe it came from (every flag, `--prompt` included), check it with `--plan`, and never run it as written.