muapi-ai-fight-scene
Generate a high-cut-density action / fight scene by first composing a 16-cell storyboard image, then driving Seedance 2.0 image-to-video off that storyboard. Stacks GPT-Image-2 (character sheet + storyboard), Nano-Banana-2 (environment concept), and Seedance 2.0 i2v.
Install / Use
npx skills add SamurAIGPT/Generative-Media-Skills --skill ai-fight-sceneInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AI & Machine LearningSupported Platforms
Our assessment of muapi-ai-fight-scene
muapi-ai-fight-scene scores 90/100 on our quality scale, 253rd of 825 AI & Machine Learning skills we index (top 31%).
Its SKILL.md is 7.9 KB long, well organised into 11 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 4,329 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 19 days ago, so muapi-ai-fight-scene is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
muapi-ai-fight-scene compared with similar skills
All 4 of these similar skills score higher than muapi-ai-fight-scene; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| muapi-ai-fight-scene (this skill)by SamurAIGPT | 90 | 4.3k | 19d ago | SKILL.md |
| claude-memby thedotmack | 100 | 94.8k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 85.9k | 13d ago | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 84.4k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 74.0k | 1d ago | CLAUDE.md |
Frequently asked questions
- How do I install muapi-ai-fight-scene?
- Run
npx skills add SamurAIGPT/Generative-Media-Skills --skill muapi-ai-fight-scene. The install tabs above show the steps for each supported agent. - Which AI agents does muapi-ai-fight-scene work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is muapi-ai-fight-scene safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is muapi-ai-fight-scene still maintained?
- The repository was last updated 19 days ago, so muapi-ai-fight-scene is actively maintained.
Skill content
View source on GitHubslug: muapi-ai-fight-scene name: muapi-ai-fight-scene version: "1.0.0" description: Generate a high-cut-density action / fight scene by first composing a 16-cell storyboard image, then driving Seedance 2.0 image-to-video off that storyboard. Stacks GPT-Image-2 (character sheet + storyboard), Nano-Banana-2 (environment concept), and Seedance 2.0 i2v. acceptLicenseTerms: true
AI Fight Scene Generator
Generate a high-cut-density action / fight scene by first composing a 16-cell storyboard image, then driving Seedance 2.0 image-to-video off that storyboard.
The core idea: action tension comes from cut density, not single-shot quality. Forcing the video model to follow a pre-drawn 4×4 storyboard grid gives you 16 distinct shots in a 15-second clip — landing punches, reverse angles, ECUs, whip-pans — that no t2v prompt could choreograph on its own.
Inputs
| Name | Type | Required | Default | Description |
|:---|:---|:---|:---|:---|
| character_description | text | yes | — | Full physical description of the fighter(s). Asymmetric details (eye colour, scar side, holster on left hip) help the model preserve identity across panels. |
| environment_description | text | yes | — | The scene setting — e.g. "cyberpunk wet back-alley, neon kanji signage, Stray-game aesthetic, rain on chrome." |
| action_script | text | yes | — | The action beat — prose or numbered beats. E.g. "Hero is cornered → blocks first punch → counter-elbow → throw opponent into trash cans → finisher." |
| style_direction | text | no | cinematic action film, anamorphic lens, high contrast, motion blur on hits | Aesthetic / look tags applied to every frame. |
| duration | int | no | 15 | Final video length in seconds. The storyboard's 16 cells map roughly 1 shot per second at default. |
| aspect_ratio | text | no | 16:9 | Output aspect — 16:9 cinematic, 9:16 vertical, 1:1 square. |
Steps
Phase A — Character Sheet
Generate a clean turnaround-style character sheet using muapi image generate (model=gpt-image-2-text-to-image):
- Prompt:
Character reference sheet of {{character_description}}. Three views — front, 3/4, profile — on a neutral grey backdrop. Studio lighting, full body, no text overlays, photoreal. Asymmetric identifying details preserved on the correct side. {{style_direction}}. - Aspect ratio:
3:2
Present the character sheet and confirm identity details look right before proceeding. This image becomes reference #1 for later phases.
Phase B — Environment Concept
Use muapi image generate (model=nano-banana-2) to design the scene/world:
- Prompt:
Wide establishing shot of {{environment_description}}. No characters in frame — environment only. Strong perspective lines, depth, atmospheric haze. {{style_direction}}. Production-design concept art. - Aspect ratio:
{{aspect_ratio}}
Nano-Banana-2 is chosen here for its reasoning-driven composition — it's better than text-to-image-only models at producing locations with believable spatial logic (chokepoints, cover, sightlines) that an action scene can use. Present for approval. This becomes reference #2.
Phase C — 16-Cell Storyboard
Compose the action onto a single 4×4 storyboard image using muapi image edit (model=gpt-image-2-image-to-image):
- Reference Images: the character sheet from Phase A and the environment plate from Phase B.
- Prompt:
Compose a 4×4 storyboard grid (16 numbered cells) for the following action sequence: {{action_script}} CHARACTER (use reference image 1 identity throughout, asymmetric details preserved): {{character_description}} LOCATION (use reference image 2 spatial layout): {{environment_description}} Each cell labels: SHOT # (1–16) · SIZE (WIDE / MS / CU / ECU) · CAMERA-MOVE arrow (push, pull, whip, dolly, crash-zoom, handheld) · 1-word RHYTHM note (BEAT / IMPACT / RECOVERY / RESET). Vary shot size aggressively — never two WIDEs in a row. Land every IMPACT on a CU or ECU. Hand-drawn comic-book ink-and-wash style, monochrome with selective red accents on hits. Numbered cells, clear gutters between panels. Aesthetic: {{style_direction}}. - Aspect ratio:
1:1(square works best for a 4×4 grid)
Present the storyboard to the user. Confirm:
- The 16 shots read clearly
- Identity stays consistent cell-to-cell
- Cut density / shot-size variation looks aggressive enough
If a panel reads poorly, regenerate just the storyboard with that cell's note bolded ("CELL 7 must be an ECU on the right fist").
Phase D — Storyboard → Video (Seedance 2.0)
Hand the storyboard to muapi video from-image (model=seedance-v2.0-i2v):
- Reference Image: the 16-cell storyboard from Phase C.
- Prompt:
Generate a {{duration}}-second action sequence that strictly follows the 16-cell storyboard reference image, cell-by-cell, top-left to bottom-right. - Honour each cell's labelled SHOT SIZE and CAMERA-MOVE — match cuts to the storyboard's rhythm notes. - Strong cinematic feel and shot language. Exaggerated dynamics. Hits land hard with motion blur and impact frames. - Camera language: anamorphic, handheld where the storyboard calls for it, locked-off where it doesn't. - Native audio: impact sfx on every IMPACT cell, footsteps, fabric/Foley, restrained low score under the action. Action being rendered: {{action_script}}. Aesthetic: {{style_direction}}. - Duration:
{{duration}}(default 15) - Aspect ratio:
{{aspect_ratio}}
After generation, present the final video. If the cut density feels too low or shots don't match the storyboard, regenerate Phase D first (cheaper than rebuilding the storyboard) with the prompt emphasising "strict cell-by-cell adherence" more aggressively.
Notes
- Why the storyboard image and not a text storyboard? Seedance 2.0 i2v anchors its motion plan to the visual reference. A grid of 16 drawn cells gives it 16 visual targets to hit — text descriptions of shots get averaged into mush.
- Asymmetric character details matter. Without something like "scar over the right eyebrow" or "leather glove on the left hand only", identity drift between cells is the #1 failure mode.
- Use
seedance-2.0-i2v-480pto draft. Cheaper preview pass before committing to the full-resseedance-v2.0-i2vrun. - For longer fights, chain two runs: first run uses storyboard A (cells 1–16, beats 1–15s); second run uses storyboard B (cells 17–32, beats 15–30s) with the last cell of A as a continuity anchor in B's first cell.
- Language: Both English and Chinese prompts work in all four models, so the storyboard cell labels can be in either language.
Trigger Keywords
fight scene, action sequence, storyboard to video, cut density, cinematic action, combat choreography, seedance 2 storyboard
Pipeline at a Glance
character_description ──► [GPT-Image-2 t2i] ─► character sheet ──┐
│
environment_description ─► [Nano-Banana-2 t2i] ─► environment plate ┼─► [GPT-Image-2 i2i] ─► 16-cell storyboard ─► [Seedance 2.0 i2v] ─► 15s action video
│
action_script + style_direction ───────────────────────────────────►┘
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>. - Phase C uses TWO reference images (character sheet + environment plate). When calling
gpt-image-2-image-to-image, pass them as a list underimages_list(or the model's documented multi-ref field). - Substitute
{{input_name}}placeholders with the user's actual inputs before issuing each call.
Related Skills
claude-mem
94.8kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
85.9kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Understand-Anything
84.4kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
headroom
74.0kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
