Update to Pixara

{
  "description": "A finished vertical or square product video with a narrator and nobody on camera: product intake, a four-slot storyboard sheet per clip through the realism pass, silent product clips with native sound, one narrator generated first on ElevenLabs V4, music on a beat grid, hard-cut assembly, captions from the script. Use when: a short product video with no one talking on camera; a product reel, a product ad or commercial, a product showcase, hands using the product with a voiceover, a launch teaser for a physical item, an app or software promo built from its screens. Not for: a person presenting on camera (presenter-video), an avatar reading a script (avatar-video), narration over illustrated scenes (faceless-explainer), product stills (product-photoshoot), listing images (amazon-listing), a cinematic story with characters (cinematic-trailer).",
  "included_files": [],
  "name": "product-reel",
  "skill_md_contents": "---\nname: \"product-reel\"\ndescription: \"A finished vertical or square product video with a narrator and nobody on camera: product intake, a four-slot storyboard sheet per clip through the realism pass, silent product clips with native sound, one narrator generated first on ElevenLabs V4, music on a beat grid, hard-cut assembly, captions from the script. Use when: a short product video with no one talking on camera; a product reel, a product ad or commercial, a product showcase, hands using the product with a voiceover, a launch teaser for a physical item, an app or software promo built from its screens. Not for: a person presenting on camera (presenter-video), an avatar reading a script (avatar-video), narration over illustrated scenes (faceless-explainer), product stills (product-photoshoot), listing images (amazon-listing), a cinematic story with characters (cinematic-trailer).\"\n---\n\n# Product reel\n\nProduce ONE finished product video in which the product is the hero and nobody talks on camera. Hands may appear; a face never does, and no identity is carried. The voice is a narrator over the clips, generated first, so the clips are cut to the words and never the reverse.\n\n## Rules that never bend\n\n- The product's shape, label and visible side survive every frame; the staging contract from intake is reused verbatim in every prompt. Exactly one hero product, no clones.\n- Claims come only from the user's own words, verbatim. With none, the narrator describes what is visible: materials, mechanism, packaging, what it does on screen. No numbers, ratings or comparisons the user did not write.\n- The narrator is generated from the exact script before any clip; every clip is sized to its take's real duration.\n- No text inside product clips. A price, a name or a line of copy is a designed frame from a text-rendering image model placed as its own short shot; captions are the subtitles tool on the master with the script, opt-in.\n- Phone-real by default: no studio strobes, no dramatic side light, no shallow depth of field, no golden hour. A cinematic look only when the brief asks for a commercial.\n- Hands only, never a face, never a real person's likeness. Hide the plumbing: display names only, no ids, no phase talk.\n\n## Intake, only for the gaps\n\nParse the brief first, then ask in one message only for what it left out: the product (a photo to upload, a URL, or a description), the duration (10, 15, 30 seconds; recommend 15), the destination and its aspect (9:16 recommended, 1:1 for a feed), whether music is wanted, the register (calm and confident, energetic). Ask only for a missing product and a missing duration. Never ask about models. Captions are the one delivery question after the master exists.\n\n## Structure\n\nOne storyboard sheet per clip, four slots each, clips of 10 to 15 seconds; the clip count follows the duration (one clip up to 15 seconds, two up to 30, three up to 45, four up to 60, then one per 15 seconds). The four slots: the product in its native context, not yet in use; demo A, the main action; demo B, a visibly different action, scale, context or target (a mouse glides, then the scroll wheel in macro; perfume mists on the wrist, then droplets on skin; a blender spins, then the pour); the result, distinct from slot one, what the product leaves behind. Hands follow the weight class from intake; a pair is one in each hand or one set down. An app or software product shows a blank device screen in the clips and its real screens as designed frames between them, never a generated interface.\n\n## Phases\n\n1. Product intake. Look at the product photo inline (or read the description) and write a one-paragraph staging contract you reuse verbatim: the object type and form, material and finish, colours, the label state (the exact printed text if legible, otherwise \"blank\" or \"unreadable\"), its size next to a hand, how it opens or is used, its weight class (heavy needs two hands and visible strain, light one relaxed hand, tiny pinched near the lens), one honest imperfection that keeps renders from looking like CGI. Lock the angle: the product shows the side the photo shows, never rotated or mirrored. Lock the claims. Derive the narrator's gender and register from the product's coding and lock them.\n2. Script. One narration segment per clip, about 2.3 words per second, two sentences at most per 10 seconds, the product named after the intro, the call to action inside the last line. The first word of every segment is content, never \"Okay\" or \"So\". Banned anywhere: \"literally\", \"obsessed\", \"game-changer\", \"changed my life\", \"hits different\", \"you need this\", \"trust me\", \"seamless\", \"effortless\". Show the script before any spend.\n3. Narration. Describe the voice in one plain sentence (gender, age range, tone, pace, accent, language) and pick a voiceId with list_voices on eleven-labs/v4 (minimax/speech-2.8 only when it fails; say so). One delivery phrase repeated verbatim on every take holds the timbre. generate_voiceover per segment (generate_batch when there are several), wait_for_jobs, then get_media_metadata on every key. A take that overruns its clip by more than a second is rewritten shorter and regenerated, never time-stretched. Passing takes are final.\n4. Sheets, one per clip, in order. generate_image on google/nano-banana-pro at 2K and 21:9 (openai/gpt-image-2 renders only 1:1, 2:3 and 3:2 on this stack, so it never makes a sheet), the product passed in imageUrls and declared in the manifest; from the second sheet on, also pass the previous sheet. Prompt: a single wide 21:9 image holding exactly four equal vertical 9:16 slots in one row on a white background with thin gutters, no labels, no text. Manifest first: \"image 1 is the product, same label, same visible side; image 2 is the previous sheet\". Per slot: the camera (locked static or a slow handheld), the distance, the action, the hands (both named, the weight class respected, safe verbs per material: a glass rests on a palm, a box is held from the sides), the product's placement, the surface and the place. Neighbouring slots never share both distance and camera. Phone aesthetic in every slot: deep focus, natural light with a direction, faint sensor noise, real surfaces, no editorial vocabulary. Then the realism pass: one image-to-image pass on bytedance/seedream-5-pro with the sheet as the input and this fixed prompt: keep the framing, the slot layout and the product exactly as they are; change only micro-realism: real material and fabric detail, even daylight with a gentle roll-off, faint sensor noise, a flat phone-camera look, deep focus, pore-level skin on any hand; no HDR glow, no teal and orange, no bokeh, no cinematic grade. The passed version replaces the raw one. Look at each sheet inline and fix a wrong beat before moving on.\n5. Clips. estimate_cost first: on this stack bytedance/seedance-2.5 costs about three and a half times minimax/hailuo-3 per second (a 10 second 9:16 clip is about 4700 credits at 720p against about 1300 at 2K) and tops out at 720p. Take Seedance for a single long take or its camera work; otherwise make the clip on minimax/hailuo-3 in reference mode with the sheet and the product in referenceImageUrls, no reference audio, the same cut list. On Seedance: reference mode with the sheet and the product in imageUrls, native audio on, the aspect, the clip length rounded up to its take; verified: it accepted a sheet with hands in it. Prompt: a style and mood line (phone footage, the light, the place); the four cuts with times that sum to the clip length (\"Cut 1, 0 to 3.5 s, static mid: ...\" then \"Hard cut to.\"), each with one action, the hands, one within-cut motion and the product's placement; a static description of the place; an Audio line naming room tone and the sounds of the actions only, \"no speech, no music\"; a quality line: one product, the label as the reference, never rotated or mirrored, no on-screen text, no subtitles, no watermark, no extra hands. Frame one is already mid-action. When Seedance refuses a sheet, fall back to the Hailuo 3 route above. Launch independent clips together with generate_batch and wait with wait_for_jobs.\n6. Music, when wanted. generate_music once on google/lyria-3.5 (instrumental) with a producer's brief: genre, mood, a named tempo, instrumentation, loop-safe, at least the piece's length. The tempo is the beat grid.\n7. Check. Tell the user what to look for in each clip unless they asked for no check-ins: the same product as the photo, the right side, believable scale, the right hands, no text. Re-render a failed clip once with the named fix; never re-render a passing clip.\n8. Assembly. get_assembly_guide once, get_media_metadata on every key, then assemble_video: the clips hard-cut in order on the base track, each sized so its take sits inside it with air on both sides; the narration takes at their moments on an audio track; the bed on a second audio track at 0.6 with duck: true; a designed price or name frame of 2.5 seconds as an image clip only when the brief carries that exact string; no text clips.\n9. Delivery. Captions through the subtitles tool on zapcap/subtitles when wanted, with referenceTranscript authored from the script, one cue per segment split into lines of at most five words and timed from the take's real start. Then one paragraph: what was made, what the voice says in one line, and two next steps (a square version, a stills set from the strongest frame).\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"
}