Trailer Maker · compétence Open Skill
Trailer Maker
create wonderful trailers
Film
141 7 36
https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/2008944/2026-09-30/ufemc4p2.jpg
# Trailer Maker Create a cinematic movie or video game trailer: background music, landscape 720p, a title card, and cinematic shots, with a total runtime of more than 2 minutes (default ~3–5 minutes). The generated video clips carry dialogue that follows the story, and the characters in each scene are relevant to that scene. ## When to use - The user wants a movie or video game trailer/teaser from an idea, one-liner, script, or reference images. - They want to revise one stage (rewrite the script, redo a shot, restyle the title card) or continue/remake the trailer. ## Reference files - None required. (This skill is self-contained.) ## Steps 1. First use `write_todos` to list the stages and update the whole list as you progress. 2. Clarify the concept if needed: movie or video game, genre/tone, the story hook or key beats, and target runtime (default ~3–5 minutes, always more than 2 minutes). If the user gave reference images, keep them for style consistency. 3. Write the trailer script/outline (logline, 4–8 key beats, the dialogue lines for each beat, and the opening and closing title card text) and save it with `create_document(content=..., name="Trailer Script", entity_type="scripts")`. Ensure the beats form a coherent, logical story that makes sense from start to finish — each beat should flow naturally from the one before it and advance the story. Do not include meaningless, filler, or disconnected scenes; every scene must serve the story. Build suspense across the beats so the trailer hooks the viewer and keeps them engaged. Confirm the beat list with the user before generating. 4. Generate the storyboard images (one per beat, plus the opening and closing title cards) with `generate_image(model='t2i', orientation='landscape', resolution='720P', name="<beat/shot title>", entity_type="storyboard_images")`. Use a reference picture at most once, purely for style/character consistency — do not use it directly to develop multiple scenes. Generate every scene's own distinct image of its own based on that picture, so each frame is unique and different from the others. Make the characters in each frame relevant to that scene — the people shown should fit the scene's story and setting. Keep a consistent cinematic style across all frames. Make allies and enemies unmistakably distinguishable at a glance in every frame: give each side a clearly different colour scheme, uniform/armour design, faction marking, silhouette, and lighting treatment, and keep that coding consistent across all scenes so the viewer can never mistake an ally for an enemy. If this is a video game trailer, keep the HUD display consistent across all frames — the same style, position, and elements (health bar, ammo, minimap, etc.) in every shot — and if the HUD marks friend/foe, use consistent friendly/hostile colours. If this is a gameplay trailer, make sure the HUD is actually displayed (visible) in the shots, including the damage feedback shown when the player character takes a hit. If the user provided reference images, pass them via `input_urls` with `model='i2i'` to keep the look consistent. 5. Animate each storyboard image into a short clip with `generate_video(model='i2v', input_urls=[<storyboard image asset_id>], orientation='landscape', resolution='720P', name="<shot title> clip", entity_type="storyboard_videos")`. Generate exactly one clip per storyboard image — never reuse a single still image to create more than one scene or clip, and never make multiple scenes from one video reference. Every clip must come from a unique, distinct storyboard image; do not repeat the same photo across multiple videos. Include the dialogue for that beat in the video prompt so the generated clip's own audio speaks the lines that follow the story. Ensure the video's own sound/audio is entirely in clear English — no gibberish, garbled, nonsense, word salad, or foreign-language phrases mixed into the conversations at all. Do not add a separate voiceover track on top of t