video-build
Skill2 starsChanged 23 days agoMITView on GitHub
Builds HyperFrames compositions for any code-built video - the project scaffold (hyperframes.json, pinned CLI, a build.py that emits the composition from measured timings), building from a real product UI (capture the real app, compose from its own classes, a measure pass), word-highlight captions in any language including Arabic and Hebrew, real footage with frame-exact windows, rendering, and a catalogue of HyperFrames, GSAP and render traps. A layer over the upstream hyperframes skills and an executor under video-studio. Use when video-studio reaches the build step of a code-built film. Triggers: "build the composition", "HyperFrames", "render the video", "add captions", "word-by-word captions", "put this footage in the video".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tymoshenko-dmytro/claude-marketing-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- tymoshenko-dmytro/claude-marketing-skills★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- ads-parserSkill
- ads-video-librarySkill
- ahrefsSkill
- competitor-researchSkill
- connectSkill
- funnel-screenshotsSkill
- ga4-reportsSkill
- gsc-insightsSkill
- image-genSkill
- parallel-researchSkill
- plain-copySkill
- seoSkill
- seo-tech-auditSkill
- video-3dSkill
- video-checkSkill
- video-generatedSkill
- video-movesSkill
- video-soundSkill
- video-studioSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 72
Keep your brand tokens (colours, fonts) in one brand-tokens.css and your trimmed logo lockups in one folder.
- Very specific: line 76
Add every new trap you hit to references/hyperframes-gotchas.md under a dated heading.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
video-build
How a code-built film is put together in HyperFrames. video-studio decides what the film
is and when it is built; this skill decides how. The upstream hyperframes,
hyperframes-core, hyperframes-animation, hyperframes-cli skills are the base
(heygen-com, used as they are); this is what was learned on top of them.
Input: the film's brief.md (../video-studio/references/brief.md). It owns copy, claims,
tone, material, moments and private data; this skill owns the implementation. If the brief
cannot be met, say so to video-studio - never change it silently.
Setup. Node.js 22+, FFmpeg, the HyperFrames CLI and its skills (the kit's
connections/hyperframes-cli.md; npx hyperframes doctor checks the toolchain). Python 3 for
build.py and scripts/footage_proxy.py (standard library only).
Start a project
references/scaffold.md: the files (hyperframes.json, package.json pinning the CLI,
build.py, assets/, audio/, timing.json, renders/), the build.py pattern (one
source, everything timed from timing.json, so the picture never drifts from the audio),
the stylesheet head, trimming identity PNGs, commands, and inspecting a render without
watching it.
Build from a real product UI
references/product-ui.md: get the real UI, compose from its own classes, measure instead
of guessing, captions word by word from the take's word timings.
Captions
node ${CLAUDE_SKILL_DIR}/scripts/captions.mjs film.json --font "Family=path" →
captions.cues.json + captions.html (paste inside the root, call mountCaptions(tl)):
word-highlight captions in any language and direction, cue breaks chosen so every cue passes
readcheck. Rules, RTL, fonts, checks: references/captions.md.
Before writing composition HTML
references/hyperframes-gotchas.md - every trap that cost a render: layout, text reveals,
media, checking, rendering, the visibility leak, overlap markers, clip-path on SVG, fonts,
encoding; real footage (<video>): exact-double times, in-points from the rendered file, priming
for the live player.
Real footage
python3 ${CLAUDE_SKILL_DIR}/scripts/footage_proxy.py CLIP --in A --out B --at T [--split] [--raw]:
<video> windows with exact-double times and the cut list from the file you render, optionally
via a 30 fps proxy that matches the engine (VFR, sparse keyframes, many windows). Rules:
references/hyperframes-gotchas.md, "Real footage".
Related executors
- Camera and editing moves, the render(t) rig, story time: video-moves.
- Sound for the film: video-sound. Gates and review: video-check.
- Generated people and scenes to assemble here: video-generated.
- Real 3D (three.js objects, globes, particles): video-3d.
Adapt it
- Keep your brand tokens (colours, fonts) in one
brand-tokens.cssand your trimmed logo lockups in one folder; every project copies them in (references/scaffold.md). - Save your first finished film as the reference project - the next one starts as a copy of it.
- Pin the HyperFrames version you tested in
package.json; bump it only after a test render. - Add every new trap you hit to
references/hyperframes-gotchas.mdunder a dated heading. - Set the caption colours from each film's own palette (
--cap-*variables), never one default.
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.