Update to Pixara

{
  "description": "A multi-shot cinematic trailer, teaser, brand anthem, fashion film, car commercial, travel teaser or game trailer run as a phased production: story, treatment, a locked style contract, anchor stills before motion, a shot list on a beat grid, clips in waves, music, then one assembled cut with a designed title. Use when: a multi-clip cinematic trailer, teaser, brand anthem or manifesto film, fashion film, car commercial, travel or destination teaser, game trailer, or short promo with a story, a look and several shots. Not for: a single clip, a talking presenter (presenter-video), a narrated explainer (faceless-explainer), a narrated story with a cast (animated-story), a product with hands and a narrator (product-reel), cutting existing footage.",
  "included_files": [],
  "name": "cinematic-trailer",
  "skill_md_contents": "---\nname: \"cinematic-trailer\"\ndescription: \"A multi-shot cinematic trailer, teaser, brand anthem, fashion film, car commercial, travel teaser or game trailer run as a phased production: story, treatment, a locked style contract, anchor stills before motion, a shot list on a beat grid, clips in waves, music, then one assembled cut with a designed title. Use when: a multi-clip cinematic trailer, teaser, brand anthem or manifesto film, fashion film, car commercial, travel or destination teaser, game trailer, or short promo with a story, a look and several shots. Not for: a single clip, a talking presenter (presenter-video), a narrated explainer (faceless-explainer), a narrated story with a cast (animated-story), a product with hands and a narrator (product-reel), cutting existing footage.\"\n---\n\n# Cinematic trailer\n\nProduce a short cinematic piece from the user's idea as a phased production, never a single generation. You play each creative role in turn and show its artifact in a few lines of prose before moving on.\n\n## Before planning\n\nAsk once, in one message, only for what the brief did not answer: the target length (about 30 seconds as a teaser, about 60 as a story), the tone or genre, and whether music or a voiceover is wanted. Recommend one option per question.\n\n## Rules that never bend\n\n- The style contract: every image and clip prompt after the style phase includes the style lines verbatim. That is what makes the clips feel like one film.\n- Anchors before motion: when a character, vehicle, object, product or place recurs across shots, never go straight to text-to-video. Establish a still first (the user's reference if supplied, otherwise a generated hero still approved by the user), then generate every shot with that subject from the same still, whichever video model the shot lands on. Prose alone drifts. A still costs a few dozen credits; re-rendering one off-model shot costs hundreds.\n- The music is briefed with a tempo before the shot list; shot lengths are whole beats or bars of that tempo; cuts land on actions.\n- Text is minimal: at most a title and an end card, each a designed frame from a text-rendering image model (google/nano-banana-pro; openai/gpt-image-2 only at 1:1, 2:3 or 3:2) with the exact string, animated with a slow move or placed as an image clip; never an assembler text clip; no text inside the shots.\n- Faces: bytedance/seedance-2.5 refuses reference images that show a realistic person, so shots with a person go to minimax/hailuo-3 in reference mode with the still as the reference (2K); a shot in which the person speaks carries its line as a recorded take in referenceAudioUrls, the way presenter-video does, never as native speech from the prompt. Seedance 2.5 takes the shots with nobody in them, where its 30 second takes and camera work shine.\n- A voiceover, when wanted, is generated on eleven-labs/v4 from an approved script and cut to its real duration.\n\n## Sub-modes\n\nThe brief decides one; it changes the arc and the anchors, never the phases: a trailer or teaser (a hook image, rising fragments, a turn, a title); a brand anthem (a belief, the world it fights, the product or people as proof, the line at the end); a fashion film (one model, three looks at most, movement as the subject, macro texture beats); a car commercial (the car as an anchor still from three angles, a location with weather, driving beats with named camera moves, one interior beat, no invented spec claims); a travel teaser (five places, dawn to night, humans only as silhouettes or hands); a game trailer (a style key, a hero character, three escalating action beats and one quiet beat, the title as a designed frame).\n\n## Phases\n\n1. Story, as a dramaturg: a logline, the theme in one line, a through-line image that resolves at the end, 6 to 10 beats with their seconds and the one turn marked.\n2. Direction, as a director: two treatment options in three lines each (world, camera language, the emotional shape, a tempo in beats per minute); recommend one, or let the user pick.\n3. Style, as a style architect: the style contract in six lines: palette (three colours by name), light, medium and grade, lens and movement vocabulary, texture (grain or the medium's surface), mood in two words; plus two negatives. Repeat them verbatim from here on.\n4. Sound first. generate_music on google/lyria-3.5 (instrumental) or minimax/music-3 (vocals) briefed like a producer: genre, mood, the tempo, instrumentation, the swell and the drop placed by seconds, at least the cut's length; a voiceover on eleven-labs/v4 (voiceId from list_voices) with the lines verbatim when wanted. Wait; get_media_metadata for the real durations. The tempo is the beat grid.\n5. Shots, as a shot planner: 6 to 12 shots of whole beats or bars, 3 to 10 seconds each (up to 30 for a Seedance 2.5 take), one line per clip: subject, action, framing distance and angle (neighbours differ), one camera move or one subject motion, sound if the model renders it, which anchor still it starts from, and the action the cut lands on. No shot opens on a settled pose.\n6. Anchors. generate_image the hero stills (a character, a product, a car, a key location) on bytedance/seedream-5-pro or google/nano-banana-pro with the style contract in the prompt; a photoreal person gets a realism pass (an image-to-image pass on bytedance/seedream-5-pro that keeps the framing and face and adds pore-level skin, real material detail, faint sensor noise, no beauty-filter smoothing); look at each inline; get the user's nod on anything that recurs.\n7. Clips in waves. Launch every independent shot together, then wait_for_job on each. Shots with a person: minimax/hailuo-3 in reference mode with the still, plus the recorded line in referenceAudioUrls when the shot speaks. Empty shots: bytedance/seedance-2.5 or google/gemini-omni-flash-1.1 with the style contract. Open every prompt with a manifest naming what each attachment is and address the subject through the reference, never also in prose. Native audio on when the model has it and the sound is wanted (name all four layers: any line after a colon, room tone, the sounds of the actions, no music); otherwise \"no speech, no music\". End every prompt with the contract lines and \"no text, no subtitles, no watermark\". Draft an uncertain shot at 720p and re-run it at 1080p with the same prompt. Retry a failure once with the named fix or on the next model with the same tags.\n8. Check. Tell the user what to look for in each clip against its shot line (the subject unchanged, the move, no text) unless they asked for no check-ins.\n9. Title and end card. One designed frame each on a text-rendering model with the exact string in the style's palette and type feel; animate the title with a slow push on google/gemini-omni-flash-1.1 (3 to 4 seconds) or place it as an image clip.\n10. Assembly. get_assembly_guide once, get_media_metadata on every key, then assemble_video: the shots on the beat grid on the base track (each trimmed to its whole beats, tighter toward the peak, one longer hold before the end, cuts by default and a fade only between scenes), the title and the end card as clips or image clips, the music bed at 0.7 (0.6 with duck: true under a voiceover), the voiceover clips at their moments, output at the delivery aspect. No text clips.\n11. Delivery. An honest paragraph: what was made, the arc in a line, which models carried what, what failed and how it was covered, and two next steps (the other aspect ratio, a 15 second cut-down).\n\n## Pixara tool mechanics\n\n- Discover: recommend_model for a goal, list_models for a service or a capability, describe_model for the exact parameters, the constraints and the price. The models named in this recipe are the ones verified for it; if one has left the catalog, take the newest model with the same tags.\n- Run: generate_image, generate_video, generate_voiceover, generate_music and the editing tools return a job id. wait_for_job(id) polls for up to 45 seconds; call it again until the job finishes. A failed job is refunded and its error names the constraint that was hit; fix that and retry once.\n- Waves: when several generations do not depend on each other (a shot list, a set of variants, the takes of a voiceover), queue them in one generate_batch call and wait for all of them with wait_for_jobs; one failing job never stops the others.\n- Results: every finished asset carries a URL and a key. Pass the URL as the input to the next generation (describe_model names the image, video and audio fields). Pass the KEY to assemble_video, and call get_media_metadata(key) for exact durations before sizing clips.\n- Inputs from the user: request_upload then finalize_upload (or upload_widget) for a local file, upload_asset for a URL, list_generations to reuse earlier work.\n- Money: prices are per model in list_models; estimate_cost before anything expensive; confirm before choosing a model that costs several times more than an alternative.\n- Seeing: images render inline, so look at every image before building on it. You cannot watch video here: when a clip finishes, tell the user what to check (face, hands, lips, unwanted text) and let them confirm before assembly, unless they asked for no check-ins.\n- Words on screen are minimal and live inside the picture: a title, a step name or a price is a designed frame from a text-rendering image model (google/nano-banana-pro at any aspect; openai/gpt-image-2 only at 1:1, 2:3 or 3:2, the only aspects it renders here) with the exact string, animated with image-to-video or placed as an image clip; the assembler's text clip is the last resort for a plain line nothing else can carry. Never ask a generation model to render text you did not receive verbatim from the user.\n- Captions never come from the assembler or a video prompt: when a piece has speech and the user wants captions, run the finished master through the subtitles tool on zapcap/subtitles with the language, a style as preset when the user wants a particular look (list_caption_styles shows them with previews; the default is clean plain text), position only when the style's own placement does not fit (a percentage of the height from 0 at the top to 80 at the bottom, around 70 for a 9:16 talking piece), and the authored script as referenceTranscript when one exists: one entry per cue with text, startTime and endTime in seconds, which keeps the script's spelling while word timing still comes from the audio. veed/subtitles is the fallback only: when ZapCap refuses the video (no audio track, longer than 30 minutes), when its job fails (one retry on VEED, never a second ZapCap run), when the captions are authored text on a piece with no speech (VEED burns them from srtContent), or when the user picked a VEED style. Never caption one piece with both. The clean master stays the master; the captioned file is the deliverable.\n- minimax/hailuo-3-max: resolution is the string \"768P\" exactly, capitals, its only value (never 480P, and a lowercase 768p is rejected); duration 5 to 15; referenceImageUrls holds at most nine.\n- Voices: eleven-labs/v4 for every voiceover (a voiceId from list_voices); minimax/speech-2.8 only when it fails; bytedance/seed-audio-1.0 for voice replication from a sample the user owns, a two-voice dialogue in one take, or spoken lines with sound effects.\n- Talk to the user in model display names, never ids, and never narrate these mechanics.\n"
}