muapi-product-ad-cinematic
About muapi-product-ad-cinematic
A muapi skill for producing a 5–10-second cinematic product ad from a product photo and brand brief. It separates low-cost hero-frame exploration from the user-approved video, upscale, and music generation phase.
Key features
- 01Four hero-frame variations
- 02User selects the frame before video generation
- 03Upscales the selected image
- 04Generates video and background music
- 05Still-image fallback if video generation fails
Use cases
- 01Developing a short product commercial from a product photo
- 02Comparing visual directions before creating an ad video
- 03Preparing a cinematic product presentation with matching music
MCP support
This is an LLM-orchestrated skill that directs an agent to call muapi CLI commands; it does not describe an MCP server or MCP-specific interface.
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/muapi-product-ad-cinematicin Claude Code to confirm it loaded.
Details
From the project READMECinematic Product Ad
Cinematic 5–10s product ad from a product photo + brand brief.
Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
product_image | image_url | yes | — | URL of the product photo (must already be uploaded). |
brand_brief | text | yes | — | Mood / style direction (e.g. "luxury minimal", "playful"). |
duration_sec | int | no | 6 | Final video length in seconds (5–10). |
Steps
This skill has TWO phases separated by a user pick. Submit them as two separate the plan calls — never bundle downstream steps into the first plan.
Phase A — variant exploration (cheap)
Submit ONE the plan containing only:
- Hero frame variants — 4 separate
muapi image generatenodes (model=nano-banana-2, aspect_ratio=16:9 by default).- Each prompt restyles the product against the brand brief mood. Vary lighting, palette, framing, and lens between variants. Keep product geometry intact.
- Reference the user's
product_imageif the model supports image conditioning; otherwise describe the product in detail.
After the plan executes, end your turn with a brief message listing the 4 asset_ids and asking the user which one to take forward (e.g. "Pick a hero (asset_1, asset_2, asset_3, or asset_4)?"). Wait.
Phase B — commit on the picked hero (expensive)
Once the user replies with their pick, submit a SECOND the plan:
- Upscale the picked frame —
enhance_image(operation=upscale). - Animate the upscaled frame —
muapi video from-image(model=kling-v3.0-standard-image-to-video, duration={{duration_sec}}, prompt="slow cinematic push-in, soft volumetric light, subtle product micro-rotation"). Reference the upscale's URL with$nX.url. - Background music —
muapi audio create(kind=music) — runs in parallel with the upscale/animate. Style derived frombrand_brief(luxury → "ambient cinematic, warm strings, slow tempo, instrumental"). Duration ≈ video length. - Return the upscaled hero image and the final video.
Notes
- If the brief mentions "luxury", bias the palette to gold/black; for "playful", bias to bright/saturated.
- If video gen fails after failover, fall back to a still-frame slideshow (just return the upscaled hero + music).
- Don't auto-confirm step 4 — its cost (~80 cr) deserves a user nod.
Trigger Keywords
product ad, commercial, cinematic ad, product video
Notes for the Executing Agent
- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call
muapiCLI commands. Usemuapi auth configurefirst ifMUAPI_API_KEYis unset. - For model IDs without a CLI alias yet, fall back to the raw endpoint via
curl -X POST https://api.muapi.ai/api/v1/<endpoint> -H "x-api-key: $MUAPI_API_KEY" -H 'content-type: application/json' -d '{...}'and poll withmuapi predict wait <request_id>. - Substitute
{{input_name}}placeholders with the user's actual inputs before issuing each call.