TimoteoAltobrando/ai-video-skill
ai-video
UnverifiedMake and edit videos with Claude Opus 5.5, end to end, from a blank page or from the user's own footage — product and launch films, ads, talking-head and founder videos, interviews, explainers, tutorials and screen demos, event and trip montages, highlight reels, podcast clips, Reels/TikTok/Shorts, animated logos and intros, music and lyric videos, and changes to a finished video (shorter cut, vertical version, subtitles, translation, new music). Remotion is the backbone; Codex (image_gen) makes images, Seedance via OpenRouter animates them, ElevenLabs makes music and sound effects, ffmpeg and whisper handle footage and speech. It starts by asking what kind of video it is and everything that kind needs (platform, format, voice, music, rights, who must not appear, budget), then goes through direction, a script or paper edit approved piece by piece, production, revisions and delivery for each platform. Use it whenever someone wants to make, cut, edit, shorten, reformat, subtitle or improve a video, even if they do not mention any of these tools.
references/direction.md
View on GitHub# Direction: principles
Read this before writing a script and at every revision: these principles prevent the corrections that otherwise come
round after round.
## Contents
1. What the video must do
2. The story
3. Words on screen
4. The interface
5. The 3D world
6. Rhythm and movement
7. Continuity and transitions
8. Brand and logo
9. Music and sound (summary)
10. Narrative films with a speaker
11. Revisions that always come
12. Working method
## 1. What the video must do
- A busy person watching without sound must understand in 5 seconds what kind of product or story it is, and by the
end what it does. If it needs explaining, the video does not work.
- Motion design is a shop window, but it comes after clarity. A beautiful abstract metaphor full of features ends up
as "you can't tell what it is about": prefer what the product really does.
- Know who the story is for. For individuals the promise is often speed ("an idea → a result in minutes"). For
companies what counts is processes with several steps, control (a person approves), reliability (it is tested) and
repetition (it runs every week).
## 2. The story
- One thread from start to end. Usually: the person with their problem → what they do in the product → the product
works → the result → it is used again and again → the closing line and the logo.
- Generic but concrete. If the product is general, do not build the video on one narrow case: use a credible, generic
process with recognisable steps (requests, data, check, document, approval, sending).
- Show what the user really does: the real fields of the product, real attachments (screenshots, spreadsheets,
documents), the real buttons. A huge block of typed text gives the wrong idea: a short description, short fields,
attachments.
- The inner complexity can be shown, but as "inside": show it for a moment, then have it swallowed by a single brand
object, which is what the user sees and uses. Otherwise the product looks like every other tool of its kind.
- Repetition conveys automation: the same run faster and faster, days passing, up to an assembly line.
## 3. Words on screen
- No titles that explain ("Step 1: describe"). The product is understood from what happens.
- Key words yes, but few, large and elegant, in the brand typeface and on the music: a word rising from below, with a
small brand mark next to it. Small technical uppercase labels look cheap: avoid them.
- Sentence style: short, second person, verb plus result, no technology named. Shapes that work:
- three or four short verbs with the same initial, one per tile or per beat;
- one sentence in two beats about the whole («Reads the request. / Prepares the answer.»);
- a human, slightly ironic tone on the automatic part («You go home. / It keeps going.»);
- a closing in three beats: what the user does, what the product does, what the user gets.
- The start and the end answer each other: if the first field of the form has a name, the closing line reuses it.
- Every sentence must be true for the product: if you say "tested", the product must test.
- Always propose 2-3 alternatives for each sentence, the recommended one first with the reason, and show them on the
real frames.
## 4. The interface
- Rebuild it in Remotion as real components (no blurry screenshots): sharp, in the brand colours and typefaces, with
the product's real labels.
- The interface is where the person acts (types, attaches, approves, runs); the mouse pointer makes it clear who does
what.
- Very fast, almost unreadable typing gives energy; the first sentence must be readable, though. A camera following
the active field gives movement without adding text.
- When the product answers, do it like a chat: words arrive in pieces. Then one clear button (for example «Approve»).
- Well-known files and programs (PDF, Word, Excel, images) are shown with their original icons, so they are
recognised at a glance (`tools.md`). They are other companies' trademarks with their own licence terms: showing them
as in a real interface is the common use, but for paid advertising have it checked by whoever handles legal.
## 5. The 3D world
- One coherent world, generated with Codex from a single reference image and animated with Seedance: a cinematic
look, a limited palette taken from the brand, soft light, few large shapes and small characters or objects in the
accent colour that "do the work".
- Avoid line-art isometric diagrams with many small objects and labels: they look old and confusing.
- Seedance clips last about 5 s. Fit them to the scenes by slowing them down (to about 0.5×) or taking a part.
Whatever must be sharp (texts, logos, numbers) is never left to Seedance.
- The split screen (4 tiles with 4 jobs in parallel) works; even better if the camera dives into one tile at a time,
the job completes, a check mark appears and it goes back to the grid.
## 6. Rhythm and movement
- First drafts tend to be slow and static; expect "more movement" in the parts made in Remotion and build it in from
the start:
- typing that speeds up;
- camera moves on the interface;
- screen splits on the beats;
- quick dives into the tiles;
- elements flying in and out;
- progressive acceleration (first calm and readable, then denser and denser).
- Every important event falls on a beat; minor ones on the eighths (every 6 frames at 24 fps and 120 BPM).
- The first time something happens it must be readable (about 1.5 s); from the second time it can speed up.
## 7. Continuity and transitions
- The same object must carry on. Wrong: an object that shrinks, stops, disappears and comes back as another object.
Right: the same object moves to its next role without stopping (it slides to the centre while the interface fades,
breaks apart, the pieces rebuild the symbol, the symbol lands on the logo).
- Transitions through the brand symbol are strong: an interface closes into the symbol; the camera enters the next
scene through the symbol.
- Cell wipes, radial waves from a button just pressed, hard cuts on the beat: choose a few and repeat them, so they
become a language. A wave of brand-coloured cells flooding the screen from the logo is a strong way to open a final
page.
- Check the joins to the pixel: the last frame of a scene and the first of the next must match where the movement is
continuous.
## 8. Brand and logo
- The logo comes from the official files (SVG); never redrawn, distorted or recoloured.
- The brand can change during a project: ask at the start which repository holds the official guidelines and check
it again when you resume. If it changes, update everything: symbol, logo, transitions, ending, objects that recall
it.
- A strong ending: the brand object in 3D breaks apart and rebuilds, the camera arrives face-on in an orthographic
view (no perspective) and the symbol lands on the SVG logo to the pixel. That is where the strongest musical hit
goes, then a wave of colour, the brand word revealed, the line and the signature.
- Other companies' logos (customers, partners, a speaker's past employers) only from their official brand pages or
verified icon sets, with their names written as the companies write them.
## 9. Music and sound (summary; details in `music.md`)
- The music follows the edit: one section per scene, with the boundaries on the bars.
- A real pause before a restart (the click on the key button silences the music for a second, then the rhythm comes
back full) is very effective.
- "More energy" usually means: deep sub, full kick, a bass riff; sub hits on the key moments (a scene entering, the
rhythm restarting, the reveal, the logo).
- Accents on the animations, not only on the cuts; real drops (a riser, half a beat of silence, the hit) on the reveal
and the logo; small sounds that follow the movements.
- Sound effects on the visual events (keystrokes, attachments landing, clicks, check marks, tiles) make a draft feel
finished at once: add them early.
- Whoever approves often watches on the phone: send the light copy and remind them the bass is heard on headphones.
## 10. Narrative films with a speaker
- **Narration, not explanation.** The voice tells a story in the first person; product details go on screen, not into
the sentences. A script that explains the product sounds like an advert read aloud.
- A structure that works for a launch: the promise everyone heard and a surprising fact from the speaker's own
experience → the ways others get it wrong → the simple question they asked themselves → what they built and tried
on themselves first → the reveal (name and one line, on the biggest hit of the music) → what changes, in a few short
beats → a line to remember (a manifesto) → a closing image → "Welcome to …".
- When in doubt, write two scripts: one that explains more and one told like a launch; let the client choose.
- **The person almost never disappears** while speaking: the room stays, with graphics around them. Full-screen
graphics are for the few beats where the voice stops or the idea needs the whole screen.
- Introduce the speaker with a lower third (name, title, company logo) and, if it helps credibility, a short
credentials slab (past companies' logos and roles).
- Interviews and testimonials without consent cannot show real faces: use roles, illustrative quotes marked as such,
waveforms, abstract portraits.
- The end of a launch film: the logo card, then a separate page with the call to action, big, for about 5 seconds.
## 11. Revisions that always come
| Request | What to do |
|---|---|
| "I can't tell what it does" | Remove metaphors and secondary features, show the real actions of the product, one thread |
| "Remove the titles" / "remove these labels" | Remove the technical labels; if needed, propose 2-3 large key words |
| "It's boring" | More movement in the Remotion parts (section 6), tighter rhythm, acceleration |
| "It looks like a huge prompt" | A short request, short fields, attachments |
| "It looks like [a competitor]" | Show the technical part as "inside" and close it into a single brand object |
| "This image isn't nice" | Replace it with a brand object or regenerate it with a reference and tighter constraints |
| "It must be continuous" | The same object from start to end of the movement, no frozen frame, pixel-exact joins |
| "The music must be cooler" | Lower and more energy, same structure; sub hits; risers before the changes; drops; mastering |
| "The logo changed" | Update official files, logo components, transitions and ending; check to the pixel |
| "They look cut out" / "everything looks fake" | `on-camera.md` section 13; often: blur the room, never repaint the wall, no double compositing |
| "The background should be blurred" | `on-camera.md` section 7 |
| "The painting doesn't follow physics" | Place it with the real perspective (`on-camera.md` section 9) |
| "Cut that silent second" | Cut picture and voice together, shift everything after it |
| "The music is still too loud" | Lower the music only and keep the master gain fixed (`music.md`); ask whether the effects go down too |
| "Add the call to action, big" | A separate final page after the logo, about 5 s, with the right link (`delivery.md`) |
## 12. Working method
- One Codex image per piece of the script, approved before animating.
- Contact sheets (key frames side by side) at every round: you look at them first, then you send them.
- Frequent drafts; when the user sends messages while you work, answer each one and carry on.
- Parallel agents help: for example one on the music, one on the 3D ending and one on a scene, each with its own
files. Give them precise briefs, with the files they must not touch, the checks to run and the report to write.
- Record every decision in the script and every expense in `docs/spend.md`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |