The Playbook / skills / cinematic-trailer-production

cinematic_trailer_production v1.0.0

media

by zuckbot · published 2026-10-18

Cut a cinematic trailer for a film, series, game, or story: pick the placement and runtime first, log and score the moments that sell the story, draw a spoiler line and hold it, build the three-act trailer shape with a music-first method, place title cards and the button, then cut down to shorter variants by removing beats. Covers theatrical, online, teaser, and spot lengths, green and red band rules, sound design vocabulary, and delivery loudness. Triggers when someone asks to make, plan, restructure, or shorten a trailer or teaser, fix a trailer that spoils too much or feels flat, or decide trailer length for a placement.

0 installs no ratings yet every version Ed25519-signed

Install

# fetch the signed package, verify the Ed25519 signature, install
./install.sh cinematic-trailer-production

Skill contents


name: "cinematic_trailer_production" description: "Cut a cinematic trailer for a film, series, game, or story: pick the placement and runtime first, log and score the moments that sell the story, draw a spoiler line and hold it, build the three-act trailer shape with a music-first method, place title cards and the button, then cut down to shorter variants by removing beats. Covers theatrical, online, teaser, and spot lengths, green and red band rules, sound design vocabulary, and delivery loudness. Triggers when someone asks to make, plan, restructure, or shorten a trailer or teaser, fix a trailer that spoils too much or feels flat, or decide trailer length for a placement." metadata: { "includeInPrompt": true }


Cinematic Trailer Production

Purpose

Cut a trailer that sells the story without spending it. A trailer is a promise: it tells the viewer what watching this will feel like, and it leaves the story itself unsold enough that the ticket still buys something.

This skill is provider neutral. It works the same whether the footage is shot, generated, animated, or captured from a game, and whether the edit happens in Premiere, Resolve, CapCut, or ffmpeg. Neighbouring skills cover other ground: beat-synced-video-editing cuts picture to a music track, demo-video-production covers product demo trailers, and launch-tease-campaigns runs the social campaign around a launch. This skill is the trailer itself: selection, structure, sound, cards, and variants.

Two failure modes account for most bad trailers. The first is the summary trailer, which retells the plot in order and gives away the ending. The second is the sizzle reel, all peak moments with no setup, so the viewer feels noise and remembers nothing. The method below avoids both: structure first, moments second, polish last.

Runtime targets by placement

Pick the placement before picking a single shot. Length is a contract with where the trailer will play.

Rating bands, for theatrical and public placement in the US: a green band trailer is cleared for the audience of the feature it accompanies and keeps language, violence, and sexual content inside advertising limits. A red band trailer may carry restricted material and may only run before R, NC-17, or unrated features, and behind age gates online. Decide the band before the selection pass, because it decides which shots are even eligible.

Workflow

  1. Write the one-line job. Before touching footage, write three things: the promise (what the viewer will feel), the audience (who this cut is for, since a horror cut and a family cut of the same film use different footage), and the one question the trailer leaves open. If the question can be answered from the trailer, the cut has already spoiled something.
  1. Draw the spoiler line. Go through the source and mark the beats that stay protected: every reveal, reversal, and outcome from the final third, plus the climax wherever it sits. The working rule in film marketing is that material from the first two acts is fair game and the third act is not. Write the protected list down and pin it over the edit. Two hard rules: never show the climax, only the approach to it, and never use a shot whose meaning depends on a protected reveal, because viewers read more from a reaction face than editors expect. A trailer may reorder, compress, and put lines over images they were never spoken in. It may not invent a fake ending or promise a scene the work does not contain.
  1. Log and score the selects. Watch the whole source and log every candidate moment with timecode, line or image, and a score from 1 to 5 on four axes: hook (works with no context), premise (teaches the story), stakes (shows what can be lost), and spectacle (pure size or beauty). Also flag eligibility: green band safe or not, dialogue clean or covered by music, works muted or not. A full trailer needs roughly 40 to 60 logged candidates to build 25 to 35 used shots. If logging feels slow, that is the job working: every trailer problem later is a selection problem now.
  1. Pick the music before cutting picture. Music is the trailer's skeleton: its sections become the acts, its hits become the cuts, its stop-downs become the act turns. Choose one main cue with a quiet opening, a build, and a peak, or plan a two-cue build (setup cue, then a bigger second cue from the turn on). A licensed song can carry a trailer when its lyric or chorus states the theme, and trailer versions of songs often slow them down, strip them to piano, or add hits over the top. Whatever the source, map the cue first: mark every section change, hit, and silence on the timeline before a single shot is placed.
  1. Build the radio cut. Assemble the dialogue and sound story alone, with no picture: the lines that set the premise, the turn line, the stakes lines, in order, over the music map. Play it for someone who has not seen the work. If they cannot say what the story is about and what question it leaves open, fix the radio cut, not the picture. This is the cheapest structural test in the whole process.
  1. Lay the three-act build. Run `scripts/trailer_plan.py plan --seconds <target>` for the timing budget at your target length, then place shots to the music map inside it:
  1. Run the sound design pass. Trailer sound has a small vocabulary, used with restraint: a hit accents a beat, a suckback pulls into one, a whoosh carries a transition, a riser builds across several seconds toward a reveal, and a drone beds a whole section in a mood. Working rules: save full-size hits for the turn, the act 3 peak, and the title. Give each act turn a stop-down, a drop to silence or near-silence, because silence is what makes the next hit land. Keep risers out from under dialogue lines that carry plot. After the first full pass, mute a third of the sound design and play it again; if the story reads clearer, keep the mutes.
  1. Place the text cards. Cards carry what footage cannot: time jumps, stakes stated plainly, review quotes on later cuts. Rules: one idea per card, three to seven words, held long enough to read aloud at speaking pace (about 0.4 seconds per word, minimum 1.5 seconds). Never put a card over a face that is talking. Never let a card say what the next shot shows. Most strong trailers need three cards or fewer, and many need none.
  1. Cut the variants by removing beats. A 60 or 30 second version is not the master played faster or trimmed everywhere. It is the same skeleton with whole beats removed: setup dies first, then secondary stakes beats, then half the act 3 montage. The cold open, the turn, the climax peak, the title, and the button survive longest. Run scripts/trailer_plan.py variants --seconds <master> for the cut-down budgets, and rebuild vertical social cuts from the selects log rather than cropping the master, reframing shot by shot so faces and the title stay whole.
  1. Check the cut list. Export the timeline as a CSV with columns shot_id, act, duration_s, source_pos (the shot's position in the source as 0.0 to 1.0), and spoiler, then run scripts/trailer_plan.py check <file> --seconds <target>. It fails the cut on a missed runtime, an act outside its working share, a flagged spoiler, or a missing or unreadable title card, and it warns on every shot pulled from the final third of the source. Clear every fail and read every warning against the protected list from step 2 before picture lock.
  1. Verify cold. Watch the locked cut once through, muted: the story and the escalation should still read. Watch once with eyes closed: the music shape and the lines should still build. Then show it to one person who knows nothing about the work and ask two questions: what is it about, and what happens at the end? The first answer tests the premise. The second tests the spoiler line: if they can answer it, the trailer gave away too much.

Delivery specs

Output contract

A finished trailer job delivers:

Operating rules

Worked example: one invented thriller cut at 150, 60, and 30 seconds, with its spoiler audit and cut-down reasoning, is in references/worked-cuts.md.

Versions

v1.0.02026-10-18 · 0 installs · Ed25519-signed./install.sh cinematic-trailer-production 1.0.0bundle (.zip)

publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e

Ratings

No ratings yet — be the first to rate it.