calesthio/generative-media-skills/cinematic-trailer-production

Claude Code and agent skill by calesthio/generative-media-skills

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Provider-independent cinematic trailer production for AI agents creating movie-style trailers, teaser trailers, launch trailers, game trailers, documentary trailers, series promos, and high-impact generated-media previews. Use for trailer strategy, structure, shot planning, voiceover/title-card copy, music and sound-design direction, generated-video prompt translation, edit pacing, platform/runtime choices, delivery handoff, rights/claims caveats, and trailer QA.

Install

npx vskill@latest install calesthio/generative-media-skills/cinematic-trailer-production

SKILL.md

Cinematic Trailer Production

Use this skill when the user wants a trailer-like video: a movie-style trailer, teaser, launch trailer, game trailer, documentary trailer, series promo, event reveal, high-impact product preview, or social cutdown that sells anticipation rather than fully explaining everything.

This is a production discipline skill, not a provider manual. Pair it with the relevant local pipeline, generation-provider skill, editing/composition skill, and delivery tool instructions before calling tools or exporting files.

Core rule

Make one promise, then escalate proof of that promise.

A trailer is not a miniature full story. It is an engineered desire machine: the audience should understand the genre, stakes, tone, and reason to care while still wanting the full release. Every beat, shot, caption, sound cue, and title card should earn attention or increase anticipation.

Start with the trailer brief

Before writing prompts or generating clips, lock these decisions:

  1. Trailer type
  • Teaser: intrigue, tone, one image or question, usually minimal plot.
  • Theatrical/hero trailer: complete emotional arc, stakes, characters/product promise, climax tease.
  • Launch trailer: availability and conversion; spectacle plus clear release/CTA.
  • Game trailer: player fantasy, mechanics, world, loop, platforms, release/CTA.
  • Documentary trailer: premise, access, central question, credibility, emotional stakes.
  • Series promo: world, ensemble, recurring engine, season hook.
  • Social cutdown: one hook, fast proof, native vertical composition, minimal dependence on sound.
  1. Audience and distribution
  • Primary platform and aspect ratio.
  • Runtime target and whether shorter cutdowns are required.
  • Sound-on versus sound-optional environment.
  • Accessibility/captions requirement.
  • Ratings, claims, disclosure, and legal review constraints.
  1. One-sentence logline
  • Format: "When [inciting pressure], [subject] must [action/choice] before [stakes/consequence]."
  • For products: "For [audience] facing [pain], [product] makes [transformation] possible by [proof/mechanism]."
  1. Hook
  • The first 3-5 seconds must contain an image, line, question, contradiction, deadline, or sonic event strong enough to survive scrolling.
  1. Emotional destination
  • Choose the final feeling: dread, awe, urgency, triumph, mystery, rebellion, tenderness, prestige, discovery, FOMO, or trust.

If the user supplies only a broad request ("make it cinematic"), ask for the missing release object, audience, platform, runtime, and must-include/must-avoid items. If production must proceed, assume a 60-90 second hero trailer plus 30/15/6 second cutdowns and state that assumption.

Runtime and format strategy

Treat platform and ad-spec facts as volatile. Re-check official platform specifications at production time, especially duration limits, AI labels, safe zones, codec requirements, ad policies, and regional rules.

As of verification on 2026-07-10:

  • YouTube video ads recommend 1080p assets in 16:9, 9:16, or 1:1, with safe zones for overlays and CTAs; Google states format-specific length varies and should be checked by campaign type. Skippable in-stream ads allow broad runtime flexibility but list best-practice durations such as 15-20 seconds for awareness/action and 2-3 minutes for consideration. Sources: Google Ads video ad specs and skippable in-stream specs.
  • YouTube upload guidance says the player adapts to vertical and square aspect ratios, and lists recommended bitrates/audio bitrates by resolution. Source: YouTube recommended upload encoding settings.
  • TikTok's ad format and functionality policy currently requires legible high-resolution video, 5-60 seconds duration, standard video sizes including 9:16, 1:1, and 16:9, audio that is not poor quality, and dynamic content rather than mostly static imagery. Product- and placement-specific TikTok spec pages can differ, so verify the selected campaign/ad product before delivery. Source: TikTok ad format and functionality policy.
  • Meta ad specs and placement rules change often and may require login or locale-specific pages. Re-check the relevant Meta Ads Guide/Business Help placement immediately before delivery.

Practical runtime map:

DeliverableBest useCommon structure
6 secondsBumper, recall, reveal stingLogo/subject + one shock/benefit + date/CTA
10-15 secondsSocial hook, paid awarenessHook + proof montage + CTA
20-30 secondsSocial trailer, launch cutHook + stakes + 3 proof shots + final card
45-60 secondsTeaser/short trailerCold open + premise + escalation + tease
75-120 secondsHero trailerThree-act emotional arc with escalation and climax tease
2-3 minutesDeep theatrical/consideration trailerMore setup, dialogue, scenes, and story texture

Prefer planning one master trailer and derivative cutdowns together. A strong 90-second hero trailer usually does not automatically become a strong 15-second ad; the short version often needs a different opening, fewer plot beats, larger captions, and a clearer CTA.

Trailer structure

Use a three-act trailer shape unless the user requests an experimental piece.

Act 1: Hook and world

Goal: establish genre, subject, tonal contract, and the reason to watch.

Typical beats:

  • Cold open: arresting image, line, sound, statistic, or question.
  • World state: where/when/what kind of reality.
  • Disruption: what changes.
  • Character/product promise: who or what carries the trailer.

Generated-media note: act 1 is where continuity is most fragile. Build a visual bible before generation: character look, environment, palette, lens language, time of day, logo/product state, and forbidden variations.

Act 2: Escalation and proof

Goal: demonstrate scale and stakes without resolving the story.

Typical beats:

  • Montage of attempts, obstacles, capabilities, or revelations.
  • Voiceover or title cards clarify the premise.
  • Music adds percussion, pulse, or harmonic lift.
  • Scenes grow in movement, contrast, stakes, and shot size.
  • Insert one quiet beat to reset attention before the final escalation.

Do not make act 2 a flat list. Each shot should answer "and therefore?" or "but then?" rather than "and also."

Act 3: Climax tease and memory device

Goal: make the audience remember the title, release moment, and feeling.

Typical beats:

  • Big turn, impossible image, confrontation, feature reveal, or emotional line.
  • Music stop, downbeat, riser, impact, or silence.
  • Title reveal.
  • Release/CTA card.
  • Optional button joke, sting, or final mystery image.

Never spoil the final resolution unless the trailer's purpose is conversion for an already-known product where clarity beats mystery.

Beat map template

Use this as a planning scaffold, not a fixed formula.

TimeFunctionPictureAudioCopy
0-3sPattern interruptImpossible image, face, motion, threat, or product transformationHit, breath, glitch, silence, or first VO lineOptional 3-6 word hook
3-10sContextEstablish world or painPulse begins"In a world..." only if intentionally genre-aware
10-25sInciting pressureThe change, mission, launch, discoveryBass, ticking, first risePremise card or line
25-45sProof montage4-8 shots showing scale/benefits/obstaclesPercussion, impacts, whooshesReviews, claims, or feature cards only if substantiated
45-60sHuman/emotional beatQuiet close-up, witness, pause, product-in-useDrop out or thin textureOne line that reframes stakes
60-80sFinal escalationFast cuts, strongest visuals, collision of forcesFull trailerization, risers, braams, hitsMinimal copy
80-90sTitle and CTATitle treatment, release date, platform, logoTail, final hitExact release/CTA/legal card

For a 30-second version, compress to: 0-2 hook, 2-8 context, 8-20 proof escalation, 20-26 climax tease, 26-30 title/CTA. For 15 seconds, skip exposition and let the first line or title card carry context.

Shot list design

Plan shots by trailer function rather than by visual prettiness.

Required shot families for most cinematic trailers:

  • Signature image: the image the audience remembers.
  • World/wide shot: scale, geography, genre.
  • Character/product hero shot: subject identity and desirability.
  • Threat/friction shot: antagonist, obstacle, pain, countdown, or market pressure.
  • Action/proof shot: movement, capability, mechanic, transformation, or consequence.
  • Human reaction shot: face, hand, breath, witness, user, fan, player, customer.
  • Texture inserts: objects, UI, evidence, maps, newspaper, controls, artifacts, particles.
  • Escalation shot: bigger motion, danger, speed, crowd, reveal, or impossible event.
  • Title/CTA shot: clean enough to carry typography.

For AI-generated video, give every shot a continuity role:

  • subject_id: recurring person/object/product.
  • setting_id: environment and time.
  • story_beat: why this shot exists.
  • camera: lens feel, movement, framing, depth.
  • action: one clear action, not a paragraph of events.
  • continuity anchors: wardrobe, logo placement, color palette, props, weather, UI state.
  • negative constraints: no extra fingers, no changing logo, no unreadable text, no random characters, no morphing, no flicker, no invented claims.
  • handoff: exact first/last frame intent if stitching shots.

Translating a trailer plan into generated-video prompts

Most video models respond better to concrete shot direction than to abstract genre labels. Translate "cinematic trailer" into specific visual, temporal, and editorial instructions.

Use this prompt stack:

  1. Continuity bible
  • Characters/products, wardrobe/materials, palette, environments, era, camera language, aspect ratio, and typography restrictions.
  1. Shot prompt
  • Subject + action + setting + camera + lighting + mood + duration + composition + continuity anchors.
  1. Motion contract
  • What moves, how fast, where the camera moves, what must stay stable.
  1. Edit intent
  • What shot precedes/follows and what beat it serves.
  1. Avoid list
  • Model-specific failure risks and legal/brand restrictions.

Example shot prompt:

A lone astronaut in a scratched white EVA suit stands at the edge of a black-glass crater under a pale blue sunrise, visor reflecting a distant city buried under ice. Slow 35mm push-in from wide to medium, subtle handheld drift, cold rim light, volumetric haze, grounded sci-fi realism, tense silence before impact. The astronaut's suit markings, orange wrist tether, and cracked left shoulder plate must match all other shots. No readable invented text, no extra people, no logo changes, no morphing helmet.

For product trailers, replace vague cinematic effects with product truth:

Macro close-up of the actual matte-black device on a walnut desk, thumb presses the side button, screen wakes to the approved dashboard UI mockup, shallow depth of field, controlled studio reflections, smooth slider move left to right, premium launch-film lighting. Keep device proportions, logo, and UI layout identical to reference. No invented UI text or unsupported feature claims.

If a model cannot preserve continuity across shots, switch to one of these strategies:

  • Generate fewer, longer shots with in-shot reframing.
  • Use reference images or locked character/product sheets if the provider supports them.
  • Use still-image keyframes plus controlled motion for hero/product shots.
  • Hide continuity seams with silhouettes, inserts, POV shots, typography, speed ramps, match cuts, whip pans, light leaks, or sound bridges.
  • Use editorial repetition: the same color, prop, shape, or sound cue can maintain identity even when exact character continuity varies.

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
223
Repository forks
47
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/calesthio/generative-media-skills/cinematic-trailer-production/badge)](https://verified-skill.com/skills/calesthio/generative-media-skills/cinematic-trailer-production)

Something wrong with this skill or its page? Tell us.