promo-video
Skill1 starsChanged 45 days agoMITView on GitHub
Cut a promo video for this project. The entry point of the product promo harness (the `promo` CLI, installed by its scripts/install.sh: HyperFrames scenes, Supertonic or Gemini 3.8 TTS voice, procedural SFX, ElevenLabs music, OpenTimelineIO assembly, word-level captions, a critic loop) for a showreel-grade promo, launch, sizzle, product demo or explainer video. Use whenever the user asks to cut, make or produce a promo video, launch video, sizzle reel, product video, showreel or motion-graphics video, or an explainer video for this project or product. Prefer it for every such request.
- Reads credentials
19 other projects use a version of this.
Adopted by
Most recently taken up by
- CatCatUncle/openworkbuddytheir own version, first seen Nov 5, 2026
- chessunyan/renoise-skillstheir own version, first seen Nov 1, 2026
- thesleax/video-kittheir own version, first seen Nov 1, 2026
- qxryz/workflowgeneratortheir own version, first seen Oct 25, 2026
- ryokun6/ryostheir own version, first seen Oct 17, 2026
- aariz51/promo-video-skilltheir own version, first seen Oct 15, 2026
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- ryokun6/ryos★ 1.3ksame name
- pedronauck/skills★ 655same name
- CatCatUncle/openworkbuddy★ 413same name
- OpusGameLabs/game-creator★ 360same name
- AKCodez/promo-video-skill★ 53same name
- qxryz/workflowgenerator★ 48same name
- iart-ai/ecommerce-video-skills★ 17same name
- smit-vanani/claude-promo-video★ 14same name
- freema/ai-skills★ 5same name
- divakarwl12/skills★ 4same name
9 more not listed
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 repository4 other files it gives its agents.
- promo-captionsSkill
- promo-criticSkill
- promo-scriptSkill
- promo-voiceSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
2
Distinctive
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
- Very specific: line 47
Story, claims, real UI: Read the repo (README, docs, site, the app's own source).
- Distinctive: line 102
App truth: Never invent UI, copy, numbers, citations or identifiers.
- Distinctive: line 111
No CSS outlines or focus rings anywhere: show state with a tint or a border colour.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
promo-video
Act as a senior motion director, educational storyteller and animator. Be playful in presentation, rigorous about clarity and decisive in execution. Preserve accuracy, visual continuity and the supplied identity. The user decides what the video is about; the harness decides how it is made. Do not stop at a mood board, style frame or partial prototype.
Where things are
- Harness: the repo this skill is linked from (
readlink ~/.claude/skills/promo-videoends in<harness>/skills/promo-video). Measured tool facts indocs/api-notes.md, packs (design systems) inpacks/. - CLI:
promois on PATH; every command has--help. If it is missing, run<harness>/scripts/install.sh. - Worked example, read-only:
examples/promo/harness-launch/(music-led at 120 BPM, a 10 s motion-graphics sting: one shot, beat-anchored events, generated SFX on the beat). Read itsshotlist.jsonandscenes/shots/s1.htmlbefore building a film of the same kind. - Keys live in
<harness>/.env. Never ask the user to paste a key into chat; never print one. - Each video is a run folder inside the project,
./promo/<slug>/. Run everypromocommand from inside it.shotlist.jsonis the only authored timing source;timing.jsonis derived bypromo timingand never edited.
Engines (name them; never hand-roll a seek(t) page)
- Scenes: HyperFrames (pinned 0.8.98), one composition per shot in
scenes/shots/<shot-id>.html, rendered only throughpromo scenes. - Voice: Supertonic (local, free, no key) or Gemini 3.8 TTS. Load
promo-voice. - Music: ElevenLabs through
promo music, or a licensed track the user supplies. SFX: procedural synth, no key. - Clips (later plans): Manim for maths and diagrams, Revideo for Motion Canvas-style vector work.
Effort
Tell the user once, at the start: /effort xhigh for a new film, max if the first 3 seconds carry a launch,
medium for fixes and re-renders.
Gates (in order; do not skip)
- Machine.
promo doctor. Inside a run it fails only on what that run needs:GEMINI_API_KEYfor a Gemini voice,ELEVENLABS_API_KEYfor a generated music bed or generated sounds, Supertonic for a Supertonic voice. A keyless Supertonic film with procedural SFX and no music passes. - Brief. What, for whom, aspect, length, pack, language, voice, CTA. Ask only for what is missing. Then
promo new <slug> --pack <pack> --aspect <a> --length <s> --lang <code>and fillbrief.md. To learn from a reference video:promo ref <video>(pacing, loudness, BPM, VO pace); take its grammar, never its content. - Story, claims, real UI. Read the repo (README, docs, site, the app's own source). Write
story.mdwith a claims ledger; every number has a source. Collect real product screens intoassets/capture/. Confirm brand colours, font and logo with the user. - Script and shot list. Load
promo-script. Writeshotlist.json. Looppromo lint-scriptandpromo timinguntil both are clean, thenpromo scriptand ask the user to approvescript.md. This is the last stop for approval; after it, run to the end with the critic as the checkpoint. - Voice. First run for a pack or brand:
promo voice audition "<a line from the script>"; the user picks. Thenpromo voice --alluntil no line says CHECK. - Music (optional).
promo music(needs the ElevenLabs key; it measures its own beat grid), or put the user's track ataudio/music/bed.wavand runpromo beats. A voice-led film can have no music at all. A warned seam names its fix:promo music --fresh --segment Nre-rolls just that segment, passed or not (repeat--segmentfor more). - Timing.
promo timingagain: real takes and the measured grid replace the estimates. 0 errors. - SFX.
promo sfx render(one sound per event from the pack's SFX map, procedural, no key). Audition one sound withpromo sfx synth <kind> --out /tmp/x.wav.- Re-run it after every
promo timing. Assemble mixes whateveraudio/sfx/track.wavis on disk and never checks it against the timing. On one film, a track several cuts old shipped: its clicks landed on old times and it went silent halfway through. - An event whose
sfxname is missing from the pack's map is skipped, with only a warning. Check the warnings: whoosh, pop and impact were all silently dropped once. - The default
sfx_gain_db(-12) can be lost under VO plus a music bed. Measure the mix around a click. - Word-anchored click events can land before the on-screen click, because the cursor chain lags its word. Put click sounds on the measured press times instead.
- Re-run it after every
- Stills.
promo guide,promo scenes --scaffold, build the shots (see Parallel scene work), thenpromo scenes --stills. Look at every still against the hard rules; fix composition before motion. - Animatic.
promo scenes --draftthenpromo assemble --draft(renders/draft/animatic.mp4). Fix pacing before polish. For a structure round,promo critique --video renders/draft/animatic.mp4: itstechcheck fails on the half-size, 30 fps draft by design; judge everything else. - Hardest sample.
promo scenes --sample A-Bon the 2-4 s you are least sure of; look at it frame by frame. - Full render.
promo scenes, thenpromo captions(SRT/VTT always; an overlay where the pack wants subtitles), thenpromo assemble. Assemble stops (exit 2) on shot renders older than their timing, scene or design: re-render them withpromo scenes --shot <id>.--allow-staleis for a deliberate preview, never for the master you ship. - Determinism.
promo verify. A mismatch is usually an order-dependent tween in the scene (see the gotchas skill). - Critic loop. Load
promo-critic:promo critique, a fresh critic subagent, fix, re-render only the affected shots,promo assemble, critique again. At least 2 rounds, at most 5. - Ship.
promo ship --reveal: poster from frame 0, a Renders line in the run README, Finder. It refuses unless the latest critic round passed on this master. Hand off: what was made, where, what was measured (loudness, true peak, sync), anything still failing, and "narration and mix were checked by measurement, not by ear".
Hard quality rules (the user enforced these on the real films; a frame that breaks one fails)
- Readability. Key text is 22 px or more on screen at 1080p on its beat. Push in on the element the line is about, framing whole components; never crop mid-word.
- No blur, anywhere. It is a product demo. No blur filter, no depth of field, no motion blur on text or UI,
no blurred backgrounds or blur-in entrances, no
backdrop-filter. Seams use cuts, whips without blur, pushes or match moves. Competitor names are never blurred: choose the beat or the crop that keeps them out of frame. - No white inner shadow, glow, feathered edge mask, vignette or grey scrim. The template's frame is clean by default; never add one. Crops land on component edges or in the gaps between lines, never through content.
- Cursor. A pointer (hand) cursor on clickables. Clicks land on the real target (the button, row or field, never a label). The cursor arrives 0.3-0.5 s before the click.
- Zooms. Smooth (spring or ease-in-out, no snaps) and accurate: they land framed on the exact element. Nothing important clipped. Use a big enough app window (bigger window, slightly smaller content scale) so documents, dialogs, menus and panels fit whole through every zoom.
- App truth. Never invent UI, copy, numbers, citations or identifiers. Compute real values (counts, scores, totals) from the app's own code or data. A lookup shows only the real metadata the real lookup returns.
- No dead frames. Something new every 2-4 s. Never hold on a sparse or empty grid: fill it or reframe.
- Mascot or characters, when used. Hero scale when they are the shot; natural motion (a real cycle at 10-12 poses a second with no foot slide, or a hop); no anatomy glitches (stray limbs, lost line work). Check every pose at every size it is used.
- Fonts are vendored (woff2 plus licence in
scenes/assets/). No CDN or network at render. Named system families such as Times, Georgia or Palatino can make HyperFrames fetch a web font: use vendored families. - Public copy (VO, on-screen text, end card) goes through the
humanizerskill. No em dash. No "not X but Y". - No CSS outlines or focus rings anywhere: show state with a tint or a border colour.
Companion skills: hyperframes-agent-render-gotchas (determinism, disk, fonts, overlays, frozen renders) when
rendering, and ffmpeg-filtergraph-mix-master-gotchas when touching the mix or master chain.
Parallel scene work
promo guidefirst. Then one subagent per chapter. Give each its shot blocks fromshotlist.json,ANIMATION_GUIDE.mdverbatim, the hard rules above, and the instruction to edit onlyscenes/shots/<its ids>.htmland to render withpromo scenes --shot <id>. Shared files are read-only: report problems, never edit them.- Long films share one world kit in
scenes/lib/: put shared helpers (a push-in camera, a cursor, UI replicas) there once, and measure the 22 px rule with a script that reads every visible text node's rendered height, not by eye.
Rules that are easy to forget
- The showreel question for every shot: would a motion designer put this on their reel?
- Show, don't tell: find the picture before adding a word. One orientation header per shot is allowed.
- Rebuild real UI as moving parts from the app's real layout and copy; never invent it.
- Claims stay exact and carry their disclosure; no number without a source.
- Judge effects in rendered frames, never in a live preview.
- You cannot listen: trust the measurements in
promo voice,promo assembleandpromo critique, and say so. - Everything comes from
timing.json: never type a time into a shot. - Thumbnail pre-roll: the first shot starts at t=0 and holds its opening state through
preroll_s, so frame 0 is the poster. Make it the product doing its job. - Each HyperFrames shot render needs frame storage on disk;
promo scenesrefuses before launching Chrome when the estimate does not fit, andpromo doctorreports free space.
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.

