chop-reel
Skill2 starsChanged 29 days agoMITView on GitHub
Fast CapCut-style chop-cut reel with a story — showreels, hype edits, launch teasers, "make it punchy". One canvas engine on a beat grid (punch-ins on cuts, flash frames, impact shakes, whip pans, speed ramps, freeze frames) rendered in HyperFrames, in 16:9 and 9:16 from one edit, with an original synthesized score locked to the cuts.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- art-stylesSkill
- caption-videoSkill
- explainerSkill
- launch-filmSkill
- product-demoSkill
- scoreSkill
- studioSkill
- ugc-actorSkill
- ugc-adsSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Write a 5–8 beat story where each beat showcases one capability and the edit itself tells it.
- Very specific: line 45
Use the score skill: copy examples/phonk_150bpm_45s.py for a full-length trap/phonk score, or extend the template's score.py.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Chop reel (HyperFrames)
Proven on "The Brief" showreel. People judge reels by pace and narrative, not polish alone — a plain montage of nice scenes reads as "basic". Give it a story with stakes.
1. Story first (before any code)
Write a 5–8 beat story where each beat showcases one capability and the edit itself tells it. The pattern that worked: hook (a problem + a clock) → work montage (one skill per section) → twist/obstacle (freeze frame, client feedback) → smash cut answer → payoff blitz → delivered → end card. A persistent HUD (clock that jump-cuts, stage label) keeps viewers oriented through fast cuts.
Then a cue sheet on a grid: 150 BPM = beat 0.4 s, bar 1.6 s (or 120 BPM = 0.5 s). Every cut, slam and caption sits on a beat; sections change on bar lines. Hook = 1 word per beat for the first 1.6–3.2 s.
2. Start from the template
cp -R templates/chop-reel videos/<name> && cd videos/<name>
../../.venv/bin/python score.py # writes assets/audio/score.wav
python3 build.py 169 # writes index.html (16:9); build.py 916 for 9:16
npx --yes hyperframes@0.8.172 lint && npx --yes hyperframes@0.8.172 render -o ../../out/<name>-169.mp4reel.js structure — edit in this order:
- Scenes:
function scene(g, l)draws a whole frame at local timel. Use relative units (W,H,M,PORT) so both aspects work;fit()shrinks text to a max width. - SHOTS:
[t0, t1, scene]— the edit.null= covered by a transition. - FX lists:
PUNCH(1.06× zoom decaying over 0.2 s on each cut + extra beats),FLASH(2-frame white on drops, half-white on section cuts),SHAKES[start, dur, amp],WHIPS(motion-blurred push between scenes, 9 sub-frame renders averaged). - Video clips (huashu art, caption-kit renders, AI shots) go on top as
<video class="clip">inbuild.pywith their own punch tweens in GSAP; the canvas draws black underneath.
3. Moves library
For named moves use the motion-prompt skill: node ~/.claude/skills/motion-prompt/scripts/motion-prompt.mjs get 001 043
returns each move's published spec (curves, durations, overshoot). Port the numbers exactly into reel.js and
cite them in a comment (// #043 whip pan: …) — the user notices when moves are "inspired by" instead of used.
Useful: #001 pop-in, #005 mask reveal, #007 count-up, #008 kinetic type, #010 overshoot, #017 mask, #020 zoom
through, #023 glitch, #024 impact shake, #038 speed ramp, #040 freeze frame, #043 whip pan, #046 smash cut.
4. Sound
Use the score skill: copy examples/phonk_150bpm_45s.py for a full-length trap/phonk score, or extend the
template's score.py. Every slam/flash in reel.js gets a hit at the same time (impact, clap, riser into drops,
record scratch on the freeze, silence before the smash cut). VO via Kokoro, ducked under; captions via caption-video.
5. Check & deliver
- Snapshot each section in both aspects and look: nothing cropped in 9:16, text ≥ 4% of short side.
- Render both, loudnorm −14 LUFS, send both. Name
out/<Title> (16x9).mp4/(9x16).mp4. - Revisions: change SHOTS / scene fns → rebuild both aspects → render.
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.

