Bring a Remotion or HyperFrames video

Ask your agent to port the video, and it rewrites the piece as a vos program whose words, colours and timings are knobs. After that, anyone changes it in the studio without code, and the next change is an edit, never another rewrite.

Port our Remotion video in ./video to vos so the team can change the words and colours.

The agent uses the vos-port skill, which the skills install puts in its directories. It needs @vosjs/cli 0.54 or later and the source's own render to compare against. The CLI reads the piece first (vos port inventory) and writes a program with every word and colour already in place (vos port scaffold), so the agent's work is the motion.

What a port keeps

• The words as text elements, each bound to a value you can retype.
• The palette as colour knobs, the source's own colours first.
• The timing as the program's timeline, with a mark on it for each scene.
• The score as a sound track with gain and fades.
• Procedural pixels (noise, grain, a scrambled line) as a small painter whose amounts are values too.

What it cannot keep yet

Masks and clip-path reveals, a colour per letter, blend modes, a shape whose colour changes live, and spring easing have no exact equivalent. The agent approximates each one and names it in the version's note, so you see what changed before you publish.

Checking it

The agent runs vos compare against the source's render: every frame scored, with a sheet of the two side by side, and any frame under the bar is named. It looks at every sheet, renders at two sizes, and proves each knob by rendering it changed. You get the watch page and the studio link; what you see there is what renders.

Only hosting it?

A finished render needs no port. vos ingest render.mp4 opens it bare, with nothing drawn over it, and vos push puts it on your shelf.

Related

• Push and pull for the version loop after the port.
• /llms.txt routes an agent to the skill by the words you use.