cue-ai 0.9.2 → 0.9.3

package/resources/skills/skills/media/core-media/upload.sh

@@ -0,0 +1,41 @@
+#!/bin/bash
+# muapi.ai File Upload
+# Usage: ./upload.sh --file /path/to/file.jpg
+# Returns: CDN URL
+
+set -e
+
+FILE=""
+JSON_ONLY=false
+JQ_EXPR=".url"
+
+while [[ $# -gt 0 ]]; do
+    case $1 in
+        --file|-f) FILE="$2"; shift 2 ;;
+        --json)    JSON_ONLY=true; JQ_EXPR=""; shift ;;
+        --jq)      JQ_EXPR="$2"; shift 2 ;;
+        --help|-h)
+            echo "Usage: ./upload.sh --file /path/to/file.jpg"
+            echo "Returns the CDN URL of the uploaded file."
+            exit 0 ;;
+        *) shift ;;
+    esac
+done
+
+if [ -z "$FILE" ]; then echo "Error: --file is required" >&2; exit 1; fi
+
+if [ -f ".env" ]; then source .env 2>/dev/null || true; fi
+if [ -z "$MUAPI_KEY" ]; then echo "Error: MUAPI_KEY not set" >&2; exit 1; fi
+
+MUAPI_BASE="https://api.muapi.ai/api/v1"
+
+[ "$JSON_ONLY" = false ] && echo "Uploading $(basename "$FILE")..." >&2
+RESP=$(curl -s -X POST "${MUAPI_BASE}/upload_file" -H "x-api-key: $MUAPI_KEY" -F "file=@${FILE}")
+
+if [ "$JSON_ONLY" = true ]; then
+    echo "$RESP"
+elif [ -n "$JQ_EXPR" ]; then
+    echo "$RESP" | jq -r "$JQ_EXPR"
+else
+    echo "$RESP" | jq -r ".url // empty"
+fi

package/resources/skills/skills/media/core-platform/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: muapi-platform
+version: 0.1.0
+description: Setup and utility scripts for muapi.ai — configure API keys, test connectivity, and poll for async generation results
+---
+
+# ⚙️ MuAPI Platform Utilities
+
+**Setup and polling utilities for the muapi.ai platform.**
+
+Configure your API key, verify connectivity, and poll for async generation results.
+
+## Available Scripts
+
+| Script | Description |
+| :--- | :--- |
+| `setup.sh` | Configure API key, show config, test key validity |
+| `check-result.sh` | Poll for async generation results by request ID |
+
+## Quick Start
+
+```bash
+# Save your API key
+bash setup.sh --add-key "YOUR_MUAPI_KEY"
+
+# Show current configuration
+bash setup.sh --show-config
+
+# Test API key validity
+bash setup.sh --test
+
+# Poll for a result (waits for completion)
+bash check-result.sh --id "your-request-id"
+
+# Check once without polling
+bash check-result.sh --id "your-request-id" --once
+```
+
+## Requirements
+
+- `curl`

package/resources/skills/skills/media/core-platform/check-result.sh

@@ -0,0 +1,37 @@
+#!/bin/bash
+# muapi.ai Check Prediction Result
+# Usage: ./check-result.sh --id REQUEST_ID [--once] [--timeout 600] [--json] [--jq EXPR]
+
+set -e
+
+REQUEST_ID=""
+ONCE=false
+TIMEOUT=600
+JSON_ONLY=false
+JQ_EXPR=""
+
+while [[ $# -gt 0 ]]; do
+    case $1 in
+        --id)        REQUEST_ID="$2"; shift 2 ;;
+        --once)      ONCE=true; shift ;;
+        --timeout)   TIMEOUT="$2"; shift 2 ;;
+        --json)      JSON_ONLY=true; shift ;;
+        --jq)        JQ_EXPR="$2"; shift 2 ;;
+        --help|-h)
+            echo "Usage: ./check-result.sh --id REQUEST_ID [--once] [--timeout N] [--json] [--jq EXPR]"
+            exit 0 ;;
+        *) shift ;;
+    esac
+done
+
+if [ -z "$REQUEST_ID" ]; then echo "Error: --id is required" >&2; exit 1; fi
+
+ARGS=()
+[ "$JSON_ONLY" = true ] && ARGS+=(--output-json)
+[ -n "$JQ_EXPR" ]       && ARGS+=(--jq "$JQ_EXPR")
+
+if [ "$ONCE" = true ]; then
+    muapi predict result "$REQUEST_ID" "${ARGS[@]}"
+else
+    muapi predict wait "$REQUEST_ID" --timeout "$TIMEOUT" "${ARGS[@]}"
+fi

package/resources/skills/skills/media/core-platform/setup.sh

@@ -0,0 +1,31 @@
+#!/bin/bash
+# muapi.ai Platform Setup
+# Usage: ./setup.sh --add-key [KEY] | --show-config | --test
+
+set -e
+
+case "${1:-}" in
+    --add-key)
+        if [ -n "${2:-}" ]; then
+            MUAPI_API_KEY="$2" muapi auth configure --api-key "$2"
+        else
+            muapi auth configure
+        fi ;;
+
+    --show-config)
+        muapi auth whoami ;;
+
+    --test)
+        muapi auth whoami > /dev/null && echo "API key is valid!" ;;
+
+    --help|-h)
+        echo "muapi.ai Platform Setup"
+        echo ""
+        echo "Usage:"
+        echo "  ./setup.sh --add-key [KEY]   Save API key"
+        echo "  ./setup.sh --show-config      Show current configuration"
+        echo "  ./setup.sh --test             Test API key validity" ;;
+
+    *)
+        echo "Usage: ./setup.sh --add-key [KEY] | --show-config | --test" ;;
+esac

package/resources/skills/skills/media/couple-grid-creator/SKILL.md

@@ -0,0 +1,47 @@
+---
+slug: muapi-couple-grid-creator
+name: muapi-couple-grid-creator
+version: "1.0.0"
+description: Create a stylized 6-box grid featuring a couple in various romantic poses and outfits, with each pose framed inside a unique cardboard box packaging.
+acceptLicenseTerms: true
+---
+
+
+# Couple Grid Creator
+
+**Create a stylized 6-box grid featuring a couple in various romantic poses and outfits, with each pose framed inside a unique cardboard box packaging.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `couple_image` | image_url | yes | — | A clear photo of the couple to maintain identity. |
+
+
+## Steps
+
+### Phase A — Multi-Pose Grid Generation
+
+If `{{couple_image}}` is not provided, ask the user to upload a photo of the couple.
+
+Once the photo is available, submit the plan with ONE step to generate the stylized grid:
+
+1. **Grid Generation** — `muapi image edit` (model=`qwen-image-edit-plus`):
+   - Reference Image: `{{couple_image}}`
+   - Prompt: `Convert the above image into an 8k portrait of both faces. Both faces should be clearly visible inside separate packaging: brown square hollow cardboard boxes. There should be 6 big boxes fully occupying the frame in a grid layout. In each box, the couple's faces should be visible, striking different decent romantic poses. Each box should feature a different costume for the couple to differentiate the scenes, with both wearing decent western wear. The background inside each box should be solid black. Maintain strict identity consistency for both the man and the woman from the reference image. Cinematic tone, sharp focus, professional photography.`
+   - Aspect ratio: 1:1 or 4:5
+
+Present the generated 6-box couple grid to the user.
+
+## Trigger Keywords
+
+`couple grid`, `romantic grid`, `packaging grid`, `couple photo box`, `stylized couple portrait`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.

package/resources/skills/skills/media/design-guide/SKILL.md

@@ -0,0 +1,73 @@
+---
+slug: muapi-design-guide
+name: muapi-design-guide
+version: "1.0.0"
+description: Create a comprehensive brand design guide — color palette, typography pairings, UI component previews, and visual identity rules with example mockups.
+acceptLicenseTerms: true
+---
+
+
+# Brand Design Guide
+
+**Create a comprehensive brand design guide — color palette, typography pairings, UI component previews, and visual identity rules with example mockups.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `brand_name` | text | yes | — | The brand or product name. |
+| `industry` | text | yes | — | Industry/niche (e.g. "fintech startup", "organic skincare", "luxury hotel chain"). |
+| `style_direction` | text | no | modern, minimal, premium | Design aesthetic (e.g. "bold and playful", "corporate and trustworthy", "dark luxury"). |
+| `primary_color` | text | no | — | Optional brand primary color (hex code or color name, e.g. "#3898EC" or "deep navy"). |
+| `existing_logo` | image_url | no | — | Optional existing logo to extract brand cues from. |
+
+
+## Steps
+
+This skill runs THREE parallel generation phases, all in a single the plan.
+
+### Phase A — Color & Typography Reference Card
+
+1. **Color palette card** — `muapi image generate` (model=`bytedance-seedream-v4.5`):
+   - Prompt: `Clean design guide color palette card for {{brand_name}} — {{style_direction}} style brand for {{industry}}. Shows 5 swatches: primary, secondary, accent, background, text. Each swatch labeled with hex code. Modern design reference card, white background, editorial typography, flat design.`
+   - If `{{primary_color}}` is given, include it: `primary color is {{primary_color}}`
+   - Aspect ratio: 16:9
+
+2. **Typography pairing preview** — `muapi image generate` (model=`bytedance-seedream-v4.5`):
+   - Prompt: `Brand typography pairing sheet for {{brand_name}} — {{style_direction}}. Shows heading font (large, bold), subheading font (medium), body font (small regular), and caption font. Includes font names, sizes, and usage rules. Clean white background, professional design reference.`
+   - Aspect ratio: 16:9
+
+### Phase B — UI Component Preview
+
+3. **UI components mockup** — `muapi image generate` (model=`gpt4o-text-to-image`):
+   - Prompt: `{{brand_name}} brand design system UI kit — {{style_direction}} for {{industry}}. Shows: primary button, secondary button, input field, card component, badge/tag, icon set sample. Consistent brand colors and fonts. Professional design spec sheet, light mode, high detail, Figma-style component documentation.`
+   - Aspect ratio: 4:3
+
+### Phase C — Brand Application Mockup
+
+4. **Real-world mockup** — `muapi image generate` (model=`nano-banana-pro`):
+   - Prompt: `{{brand_name}} brand identity applied to real-world mockups — {{style_direction}} style for {{industry}}. Shows business card, letterhead, and mobile app icon all with consistent brand identity. Professional brand presentation, clean background, photorealistic mockups.`
+   - If `{{existing_logo}}` provided, use `muapi image edit` (model=`nano-banana-pro-edit`) with it as reference.
+   - Aspect ratio: 4:3
+
+After all assets generate:
+- Present all 4 assets together as a cohesive design guide
+- Provide a written text summary with: suggested font stack, hex codes, spacing rules, and do/don't guidelines
+- Offer to generate a social media template or logo next
+
+## Notes
+- All prompts should reinforce {{style_direction}} consistently across all phases.
+- If {{primary_color}} is blank, derive one from the {{industry}} and {{style_direction}} context.
+
+## Trigger Keywords
+
+`design guide`, `brand guide`, `style guide`, `design system`, `brand identity`, `visual identity`, `brand colors`, `typography`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.

package/resources/skills/skills/media/drone-style-video/SKILL.md

@@ -0,0 +1,61 @@
+---
+slug: muapi-drone-style-video
+name: muapi-drone-style-video
+version: "1.0.0"
+description: Generate aerial drone-perspective footage — sweeping bird's-eye views, orbit shots, and flyover sequences for landscapes, architecture, and events.
+acceptLicenseTerms: true
+---
+
+
+# Drone-Style Video
+
+**Generate aerial drone-perspective footage — sweeping bird's-eye views, orbit shots, and flyover sequences for landscapes, architecture, and events.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `location_or_subject` | text | yes | — | What to shoot from above (e.g. "mountain valley at sunrise", "luxury villa by the ocean", "crowded city intersection"). |
+| `shot_type` | text | no | reveal | Camera movement style — 'reveal' (ascend & reveal), 'orbit' (circle subject), 'flyover' (pass over), 'top-down' (bird's eye static). |
+| `style` | text | no | golden hour, cinematic, 4K, ultra-detailed | Visual atmosphere (e.g. "dramatic storm clouds", "misty morning", "blue hour city lights"). |
+| `aspect_ratio` | text | no | 16:9 | Output aspect ratio. |
+| `reference_image` | image_url | no | — | Optional aerial/location reference image. |
+
+
+## Steps
+
+### Phase A — Generate Drone Footage
+
+Submit the plan with ONE step:
+
+1. **Aerial video** — If `{{reference_image}}` is provided, use `muapi video generate` (model=`veo3.1-image-to-video`); otherwise use `muapi video generate` (model=`veo3.1-text-to-video`).
+   - Build prompt based on `{{shot_type}}`:
+     - **reveal**: `Drone camera starts low, slowly ascends and reveals {{location_or_subject}}, sweeping wide aerial perspective, {{style}}`
+     - **orbit**: `Drone camera orbits {{location_or_subject}} in a smooth circular arc, 360-degree aerial rotation, {{style}}`
+     - **flyover**: `Drone camera flies low and fast over {{location_or_subject}}, tracking forward momentum, depth of field, {{style}}`
+     - **top-down**: `Perfect overhead bird's eye view of {{location_or_subject}}, drone looking straight down, minimal distortion, {{style}}`
+   - Append to all prompts: `DJI-quality drone footage, stabilized gimbal, no shake, cinematic color grade, photorealistic`
+   - Aspect ratio: `{{aspect_ratio}}`
+
+After generation, offer:
+- A different shot type variation
+- Adding wind/ambient audio via `mmaudio-v2-video-to-video`
+- Upscaling via `ai-video-upscaler-pro`
+
+## Notes
+- For architecture, emphasize "slow orbit to reveal full building facade".
+- For landscapes, use "magic hour lighting" for the best results.
+- `veo3.1-text-to-video` produces the best physics and camera motion for aerial scenes.
+
+## Trigger Keywords
+
+`drone`, `aerial`, `bird's eye`, `flyover`, `aerial shot`, `drone footage`, `top down`, `overhead video`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.

package/resources/skills/skills/media/fashion-try-on/SKILL.md

@@ -0,0 +1,61 @@
+---
+slug: muapi-fashion-try-on
+name: muapi-fashion-try-on
+version: "1.0.0"
+description: Virtually try on different outfits by combining a person's photo and a clothing item, then optionally generate a professional fashion model video.
+acceptLicenseTerms: true
+---
+
+
+# Fashion Try-On
+
+**Virtually try on different outfits by combining a person's photo and a clothing item, then optionally generate a professional fashion model video.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `person_image` | image_url | yes | — | A photo of the person or model who will try on the clothes. |
+| `clothing_image` | image_url | yes | — | A photo of the clothing item to try on. |
+
+
+## Steps
+
+### Phase A — Virtual Try-On
+
+If `{{person_image}}` or `{{clothing_image}}` is not provided, ask the user to upload them.
+
+Once both images are available, submit the plan with ONE step to perform the try-on:
+
+1. **Fashion Try-On** — `muapi image edit` (model=`qwen-image-edit-2511`):
+   - Reference Images: Use both `{{person_image}}` and `{{clothing_image}}`.
+   - Prompt: `A high-quality fashion photograph of the person from the first reference image wearing the exact clothing item from the second reference image. The fit should be natural and realistic, maintaining the person's pose and the clothing's texture and patterns. Soft studio lighting, neutral background, professional fashion photography style.`
+   - Aspect ratio: 1:1 or 4:5
+
+Present the resulting fashion photo to the user for approval.
+
+### Phase B — Fashion Video Generation (Optional)
+
+After the image is generated, ask the user if they would like to create a professional fashion video of the model wearing the outfit.
+
+If requested, submit the plan with ONE step:
+
+1. **Fashion Video Generation** — `muapi video from-image` (model=`seedance-v1.5-pro-i2v-fast`):
+   - Reference Image: The try-on image generated in Phase A.
+   - Prompt: `Shot type of Three-Quarter Length Shot. [Push in] as model gracefully places hand on hip, shifts weight to one side, tilts head slightly with soft smile, and gently adjusts hair with fingertips, creating elegant movement and confidence.`
+   - Aspect ratio: 9:16 or 4:5
+
+After generation, present the final fashion video.
+
+## Trigger Keywords
+
+`fashion try on`, `virtual fitting room`, `try on clothes`, `model fashion`, `clothing preview`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.

package/resources/skills/skills/media/floor-plan-rendering/SKILL.md

@@ -0,0 +1,56 @@
+---
+slug: muapi-floor-plan-rendering
+name: muapi-floor-plan-rendering
+version: "1.0.0"
+description: Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.
+acceptLicenseTerms: true
+---
+
+
+# Floor Plan Rendering
+
+**Design a 2D floor plan and convert it into a realistic, high-quality 3D architectural rendering.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `floor_plan_description` | text | yes | — | Description of the floor plan (e.g. "a modern 2-bedroom apartment with a balcony and open kitchen"). |
+| `base_plan_image` | image_url | no | — | Optional 2D floor plan image to use as a starting point. |
+
+
+## Steps
+
+### Phase A — 2D Floor Plan Design
+
+If `{{base_plan_image}}` is not provided, submit the plan with ONE step to create the 2D blueprint:
+
+1. **Floor Plan Generation** — `muapi image generate` (model=`nano-banana-2`):
+   - Prompt: `A professional, clean 2D architectural floor plan of {{floor_plan_description}}. Top-down view, technical drawing style, white background, black lines, labeled rooms (Living Room, Kitchen, Bedroom, etc.), high contrast, minimalist design.`
+   - Aspect ratio: 4:3 or 1:1
+
+Present the 2D plan to the user for approval.
+
+### Phase B — 3D Rendering
+
+Once the 2D plan is ready, submit the plan to convert it into a realistic 3D visualization:
+
+1. **3D Conversion** — `muapi image edit` (model=`nano-banana-2-edit`):
+   - Reference Image: The 2D plan from Phase A.
+   - Prompt: `A stunning, realistic 3D isometric cutaway rendering of the architectural floor plan. Photorealistic textures, warm wooden flooring, modern furniture, soft natural sunlight coming from windows, realistic shadows. High-end architectural visualization, cinematic look, 8k resolution, clean white studio background.`
+   - Aspect ratio: 4:3 or 1:1
+
+After generation, present the final 3D rendering to the user.
+
+## Trigger Keywords
+
+`3d floor plan`, `architectural rendering`, `2d to 3d plan`, `house design`, `interior plan`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.

package/resources/skills/skills/media/freeze-effect-video/SKILL.md

@@ -0,0 +1,100 @@
+---
+slug: muapi-freeze-effect-video
+name: muapi-freeze-effect-video
+version: "1.0.0"
+description: Generate a cinematic "freeze effect" video where time stops mid-scene, the subject walks through the frozen world, then time resumes with a snap.
+acceptLicenseTerms: true
+---
+
+
+# Freeze Effect Video
+
+**Generate a cinematic "freeze effect" video where time stops mid-scene, the subject walks through the frozen world, then time resumes with a snap.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `photo` | image_url | yes | — | Reference photo of the main character (face/body) whose appearance must remain consistent across all shots. |
+| `scene` | text | no | a packed, dimly lit sports bar with neon accents, blurred TVs showing a championship celebration | The setting where time will freeze (e.g. "a busy nightclub", "a wedding reception", "a stadium crowd"). |
+| `freeze_moment` | text | no | golden arcs of beer suspended midair, popcorn floating motionless, people frozen mid-cheer | The signature frozen visual — what hangs in the air when time stops. |
+| `closing_line` | text | no | perfect | A short word/phrase the character whispers before resuming time. |
+| `aspect_ratio` | text | no | 16:9 | Output aspect ratio — "16:9" for cinematic, "9:16" for vertical/social. |
+| `duration` | text | no | 15 | Target duration in seconds (10 or 15 recommended). |
+
+
+## Steps
+
+### Phase A — Generate the Freeze Effect Video
+
+Submit the plan with ONE step:
+
+1. **Freeze effect video** — `muapi video from-image` (model=`seedance-v2.0-i2v`, quality=`high`, generate_audio=`true`):
+   - Reference image: `{{photo}}`
+   - Aspect ratio: `{{aspect_ratio}}`
+   - Duration: `{{duration}}`
+   - Resolution: `720p`
+   - Prompt:
+     ```
+     Ultra-realistic, shot on Arri Alexa Mini, 35mm lens, {{scene}}, volumetric haze, dynamic hard shadows, shallow depth of field.
+
+     Main Character:
+     The person from @image1. Facial features and body proportions remain consistent across all shots.
+
+     [0:00–0:03]
+     {{scene}}. Time flows normally.
+     Steadicam frontal medium shot tracking the person walking confidently through the crowd.
+     The crowd erupts in euphoria around them.
+     As the person walks, they raise their right hand and snap.
+
+     [0:03–0:06]
+     At the snap, a subtle spherical shockwave bursts from their fingertips — air distortion and light refraction ripple outward.
+     Everything freezes mid-motion.
+     {{freeze_moment}}.
+     Neon light catches dust and liquid in the air.
+     Absolute silence.
+
+     [0:06–0:09]
+     Only the person moves.
+     Soft, echoing footsteps.
+     Camera tracks backward as they walk through the frozen scene, observing calmly.
+     They reach out and pluck a single suspended detail from the air.
+
+     [0:09–0:11]
+     They stop in front of a frozen onlooker, face locked in an ecstatic expression.
+     The person tilts their head, gently observes.
+     Softly: "{{closing_line}}".
+
+     [0:11–0:15]
+     They turn, face the camera, smirk, and snap again.
+     A stronger reverse shockwave ripples outward.
+     Motion instantly resumes — sounds explode back, people land mid-jump.
+     The person walks away as the camera pushes through the celebrating crowd.
+
+     Fade to black.
+
+     Sound Design:
+     Deafening ambient celebration → snap → deep shockwave/bass drop → absolute silence → footsteps → soft whisper → snap → reverse shockwave → deafening celebration returns.
+     ```
+
+After generation, present the video to the user.
+
+## Notes
+- The character's identity is anchored by `@image1` — the reference photo must clearly show the main subject's face.
+- For best results, choose a `scene` with crowd energy and lots of small objects (liquid, confetti, sparks) that can plausibly "freeze" in midair.
+- If the model rejects realistic human likeness, switch to the Global tier model (`seedance-2-image-to-video-fast`) which allows looser identity matching.
+- For vertical/social delivery, set `aspect_ratio=9:16` and keep `duration=10` for tighter pacing.
+- Always keep `generate_audio=true` — the snap → silence → snap audio arc is the signature of this effect and should not be muted.
+
+## Trigger Keywords
+
+`freeze effect`, `time freeze video`, `time stop video`, `snap freeze`, `frozen world`, `bullet time crowd`, `time stand still`, `pause time effect`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.

package/resources/skills/skills/media/giant-product-showcase/SKILL.md

@@ -0,0 +1,61 @@
+---
+slug: muapi-giant-product-showcase
+name: muapi-giant-product-showcase
+version: "1.0.0"
+description: Create a dramatic "Giant Product" visual where a regular item is showcased as a massive, building-sized object next to a person, then optionally animate the scene.
+acceptLicenseTerms: true
+---
+
+
+# Giant Product Showcase
+
+**Create a dramatic "Giant Product" visual where a regular item is showcased as a massive, building-sized object next to a person, then optionally animate the scene.**
+
+## Inputs
+
+| Name | Type | Required | Default | Description |
+|:---|:---|:---|:---|:---|
+| `product_image` | image_url | yes | — | A clear image of the product to be made giant. |
+| `person_description` | text | no | a stylishly dressed man | Description of the person standing next to the giant product. |
+
+
+## Steps
+
+### Phase A — Giant Product Visualization
+
+If `{{product_image}}` is not provided, ask the user to upload a photo of the product.
+
+Once the photo is available, submit the plan with ONE step to create the giant product scene:
+
+1. **Scene Generation** — `muapi image edit` (model=`nano-banana-2-edit`):
+   - Reference Image: `{{product_image}}`
+   - Prompt: `A professional commercial photograph featuring a massive, giant-sized version of the product from the reference image. The product is the size of a person and is standing on a clean, modern floor. Next to the giant product, {{person_description}} is leaning against it or standing nearby, highlighting the enormous scale. High-end product photography, soft studio lighting, realistic reflections, 8k resolution.`
+   - Aspect ratio: 3:4 or 4:5
+
+Present the generated giant product image to the user for approval.
+
+### Phase B — Animation (Optional)
+
+After the image is generated, ask the user if they would like to animate the scene into a cinematic showcase video.
+
+If requested, submit the plan with ONE step:
+
+1. **Video Generation** — `muapi video from-image` (model=`veo3.1-fast-image-to-video`):
+   - Reference Image: The giant product image from Phase A.
+   - Prompt: `Cinematic slow-motion camera movement around the giant product. The person next to it moves naturally, looking at the camera or adjusting their pose. Dynamic lighting, high-quality textures, professional commercial vibe.`
+   - Aspect ratio: 9:16 or 4:5
+
+After generation, present the final product showcase video.
+
+## Trigger Keywords
+
+`giant product`, `massive object`, `product showcase`, `scale comparison`, `product animation`
+
+
+---
+
+## Notes for the Executing Agent
+
+- This recipe is LLM-orchestrated: read each phase, gather any missing inputs from the user, then call `muapi` CLI commands. Use `muapi auth configure` first if `MUAPI_API_KEY` is 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 with `muapi predict wait <request_id>`.
+- Substitute `{{input_name}}` placeholders with the user's actual inputs before issuing each call.