samuraigpt/muapi-one-shot-video
Generate a single continuous cinematic shot video — no cuts, one seamless flowing scene with dramatic lighting and motion.
npx skills add https://github.com/SamurAIGPT/Generative-Media-Skills --skill muapi-one-shot-video
Generate a single continuous cinematic shot video — no cuts, one seamless flowing scene with dramatic lighting and motion.
| Name | Type | Required | Default | Description |
|:---|:---|:---|:---|:---|
| scene | text | yes | — | The scene to render (e.g. "a chef plating food in a moody Michelin-star kitchen"). |
| style | text | no | cinematic, anamorphic lens, shallow depth of field, dramatic lighting | Visual tone and style (e.g. "noir, handheld, golden hour"). |
| duration | text | no | 10s | Target duration (e.g. "5s", "10s"). |
| aspect_ratio | text | no | 16:9 | Output aspect ratio — "16:9", "9:16", or "1:1". |
| reference_image | image_url | no | — | Optional reference image for subject/scene anchoring. |
Submit the plan with ONE step:
{{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).{{scene}}, one continuous uncut shot, no transitions, camera slowly moves through scene, {{style}}, ultra cinematic, film grain, 4K quality{{aspect_ratio}}{{duration}}After generation, present the video and suggest:
mmaudio-v2-video-to-videokling-v3.0-pro-image-to-video as an alternative for better human motion.one shot video, single take, continuous video, one take, cinematic shot, seamless video
muapi CLI commands. Use muapi auth configure first if MUAPI_API_KEY is unset.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>.{{input_name}} placeholders with the user's actual inputs before issuing each call.Take samuraigpt/muapi-one-shot-video from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.