agentleFS
full-aigc-skillsfull-aigc-skills/minimax-skills/skills/3d-animation-short-generator/SKILL.md

3d-animation-short-generator

Skill4 starsChanged 58 days agoApache-2.0View on GitHub

Create complete stylized 3D animated shorts from a story idea through an ordered production workflow covering project brief, story outline, character and environment cards, standardized shot planning, text or optional pencil storyboards, video-model selection, single-shot generation, assembly, BGM matching, and final review. Use when the user wants an end-to-end narrative animation workflow with strong character consistency, scene continuity, timing, camera, performance, and audio control. Not for single images, simple edits, photorealistic live action, or one standalone clip.

  • Installs packages

9 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

23 rules. 14 are common, 0 are distinctive, and 9 are very specific to this project.

  • 14

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Create or later update episode artifacts in this order:

    line 82
  2. Very specific:

    Do not dump long production content only in chat.

    line 94
  3. Common:

    Only proceed after the user chooses or explicitly says to continue.

    line 120
  4. Very specific:

    Create a story outline and write it to a markdown file story-outline.md.

    line 124
  5. Common:

    After the main character cards are generated, show a user choice card:

    line 174
  6. Common:

    Add another character card

    line 179
  7. Common:

    Add another scene angle

    line 199
  8. Common:

    After character cards and scene cards are locked, output standardized video prompts as a shot information table.

    line 204
  9. Very specific:

    Create a canvas table node named 标准镜头信息表 or standard-shot-table.

    line 210
  10. Very specific:

    Use exactly six columns: Shot ID & Duration, Continuity Handoff, Reference Anchors (Spatial + Identity), Hook Type, Shot Description …

    line 211
  11. Common:

    Every row must include complete per-second directives, continuity handoff, reference anchors, hook type, and audio/dialogue timing.

    line 212
  12. Very specific:

    Run the Step 5.5 self-check from references/shot-table-spec.md before storyboarding.

    line 213
  13. Common:

    After the Step 5.5 self-check passes, show a storyboard-mode choice card before producing any storyboard artifact.

    line 219
  14. Common:

    Default mode is one authoritative text storyboards document containing one section per shot.

    line 225
  15. Common:

    After all storyboards are approved, proceed to the video-model choice card.

    line 230
  16. Common:

    Before any clip is rendered, show the video-model choice card and resolution choice card.

    line 234
  17. Very specific:

    Read references/model-selection.md for the H3 default, Seedance 2.0 fallback, per-shot mixed mode, resolution choices, and model-specific …

    line 238
  18. Very specific:

    Read references/fallback-policy.md for per-model retry ladders, drift handling, and escalation choices.

    line 239
  19. Very specific:

    If a clip drifts from the approved Reference Anchors, follow references/fallback-policy.md.

    line 248
  20. Very specific:

    After all clips render, place them on canvas in shot order, group them as <title> shot clips, and show the clip approval card defined in …

    line 250
  21. Common:

    After all single-shot clips are approved, assemble the complete main video, match or generate one continuous BGM track, and produce the …

    line 254
  22. Common:

    Use only approved latest assets.

    line 261
  23. Common:

    Do not add subtitles or text unless explicitly requested.

    line 263

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tool mapping (mmx-cli edition)

This skill is the mmx-cli adaptation of the MiniMax-H3 Hub skill of the same name: the creative methodology is unchanged, while Hub canvas tools are replaced by the following portable equivalents.

Hub toolmmx-cli / portable equivalent
hub_generate_imagemmx image generate --prompt "..." --out <path>
hub_generate_videommx video generate --prompt "..." --out <path> (Hailuo; see mmx video generate --help for duration/model flags)
hub_generate_audio / hub_synthesize_speechmmx speech synthesize --text "..." --out <path.mp3>
hub_generate_musicthe minimax-music-gen skill (MiniMax music API; mmx has no music command)
hub_video_editffmpeg assembly (concat / xfade / audio mix) — deterministic, offline
hub_analyse_mediaffprobe + mmx vision describe <file>
hub_image_searchuser-provided assets first; mmx search query "..." for public references
hub_canvas_get_node / hub_canvas_group_recent_outputsthe episode working directory: assets-manifest.md, outputs/, decisions.md ledger files
choice cardsnumbered options presented in chat, choice recorded in decisions.md

Prerequisites: npm install -g mmx-cli and mmx auth login --api-key sk-xxx (region auto-detected; mmx quota shows the Token Plan balance). ffmpeg/ffprobe must be on PATH for assembly and inspection.

3D Animation Short Generator

Use this Skill when the user wants a complete story-first animated short workflow, from one-line idea to final edited video. The workflow must save every major artifact to the episode working directory in production order and pause at creative gates with numbered options (recorded in decisions.md) before expensive or high-impact steps.

Core rule: story first, ask screen size and total duration with numbered options immediately after user intake, ordered episode artifacts, every required confirmation via numbered options, fixed order after character/scene cards: six-column standardized shot table with per-second directives + audio cues + spatial anchor chain → shot-table self-check gate → one single text storyboards document with one section per shot (multi-panel pencil image only when user explicitly opts into visualization mode; any shot flagged for heavy iteration is extracted to a standalone text storyboard node) → video-model decision (H3 default, Seedance 2.0 fallback) + resolution decision → single-shot clips rendered by the chosen video model → full-film assembly with BGM; final video must remove all storyboard artifacts.

Global Visual Style Lock

Unless the user explicitly requests another visual style, all character cards, scene cards, shot tables, text storyboards, optional pencil storyboards, single-shot video clips (regardless of which video model is selected), assembled videos, and final composites must use this visual style:

  • Rendering style: Pixar-inspired 3D cartoon rendering, C4D + Octane renderer look, high-end animated feature quality.
  • Character design: exaggerated geometric simplification balanced with excellent material detail. Avoid 100% realistic human anatomy; use high-level shape language, large readable silhouettes, and Q-version proportions when appropriate.
  • Proportion language: friendly stylized proportions, often 2.5–3 head-tall for cute or childlike characters, with big heads, compact bodies, clear silhouettes, and high recognizability.
  • Hair / fur: combine strong sculpted clumps and clean block shapes with fine edge flyaway hairs or fuzzy rim details, so hair/fur feels designed but tactile under light.
  • Skin / material: warm subsurface scattering skin quality, soft translucent reddish light through ears, cheeks, nose, and fingertips; avoid hard plastic skin.
  • Acting style: exaggerated, lively Disney/Pixar-style character animation performance with squash and stretch, strong brows, eye corners, pupils, lips, and cheek shape changes.
  • Motion style: high-energy poses, clear line of action, forward lean, strong anticipation, fast but readable timing, elastic body mechanics, and vivid micro-expressions.
  • Emotional range: balance cuteness and explosive expressiveness; intense emotions may use dramatic facial deformation while preserving character appeal.

Negative style constraints: no photorealistic live-action, no flat 2D anime, no plastic toy skin, no stiff mannequin posing, no realistic anatomical stiffness, no lifeless facial expressions.

STEP 0: Intake and Canvas Plan

Capture:

  • One-line idea or rough premise
  • Desired output: blueprint only, assets only, standardized shot table with per-second directives, single text storyboards document (default) + extracted single-shot text storyboard nodes for heavy-iteration shots + multi-panel pencil storyboards (opt-in), single-shot video clips (with video model chosen in Step 7), assembled main video, or final BGM-composited film
  • Approximate length, if the user already stated it
  • Screen size / aspect ratio, if the user already stated it
  • Visual tone: default warm stylized 3D animation
  • Dialogue requirement: whether the film has dialogue, voiceover, or no speech
  • Dialogue language only if the user explicitly states it; do not default to English dialogue

Immediately after capturing the user's input, before Project Brief or any other next step, show choice cards to confirm production format:

Screen size / aspect ratio card:

  • 16:9 landscape (recommended for cinematic short)
  • 9:16 vertical short
  • 1:1 square
  • 4:5 social portrait
  • Custom size / aspect ratio

Total duration card:

  • 30–60 seconds (recommended)
  • 15–30 seconds
  • 60–90 seconds
  • 90–180 seconds
  • Custom duration

Only proceed after the user chooses both screen size/aspect ratio and total duration, or explicitly supplies custom values. Store the approved screen size/aspect ratio and duration in the Project Brief and reuse them in shot timing, transition continuity, the standardized shot table with per-second directives, single-shot storyboards (text by default, pencil image when user opts in), single-shot video clips, assembly, BGM matching, and final composite settings.

Create or later update episode artifacts in this order:

  1. Project Brief text node
  2. Story Outline text node
  3. Labeled Character Card image nodes
  4. Environment-only Scene Card image nodes
  5. Standardized Shot Information Table node with six columns; each row must include per-second directives inside Shot Description
  6. Single text storyboards document — one markdown file named <title> text storyboards containing one section per shot (mirrors the half-narrated-drama storyboard structure). When the user flags a shot for heavy iteration, that section is extracted to a standalone markdown file and an (extracted) marker is left in the document. Pencil image storyboards, if opted in, are separate image files.
  7. Single-Shot Video Clip nodes (rendered by the video model selected in Step 7 — H3 default, Seedance 2.0 fallback)
  8. Assembled Main Video node
  9. Matched BGM audio node and Final BGM-Composited Video node

Do not dump long production content only in chat. Save durable outputs as markdown/image/video/audio files under the episode directory.

STEP 1: Project Brief

Produce a concise project brief and write it to a markdown file named with the project title or 项目简报.

Include:

  • Working title
  • One-line What-if
  • Emotional premise
  • Target audience feeling
  • Main deliverables planned
  • Approved screen size / aspect ratio
  • Approved total duration
  • Dialogue mode and language: only use a specific language when the user explicitly requested it; otherwise write language not specified and keep dialogue minimal or ask later when needed
  • Initial risks
  • Dialogue intent when present

Then present the numbered options to the user:

  • Continue with this direction (recommended)
  • Regenerate premise options
  • Revise emotional premise
  • Refine dialogue direction

Only proceed after the user chooses or explicitly says to continue.

STEP 2: Story Outline and Gates

Create a story outline and write it to a markdown file story-outline.md.

Include:

  • Protagonist Want / Need / flaw
  • Core world rule
  • 8-beat causal story spine
  • Emotional anchor and payoff
  • Dialogue beats if the user requested dialogue
  • Red-line checks

Gate checks:

  • Protagonist is active
  • Crisis is intensified by protagonist flaw
  • Coincidence never solves the problem
  • Ending reuses an earlier emotional anchor
  • Antagonistic pressure is not a flat villain
  • Dialogue reveals relationship change instead of explaining the theme

Then present the numbered options to the user:

  • Approve story and continue (recommended)
  • Revise beats
  • Revise emotion curve
  • Revise dialogue beats
  • Return to premise

STEP 3: Character Cards

Generate character reference cards and save each image under outputs/. Recommended order:

  1. Protagonist card
  2. Contrast / pressure character card
  3. Optional supporting character card

Each character card should be a 16:9 production reference sheet when possible. Unlike final rendered video, character cards should include clear readable labels so downstream generation can bind the correct person and props:

  • Character name label in English and/or the project language
  • Role label, such as protagonist, grandma, thief, sidekick, pressure character
  • Main 3/4 view
  • Front / side / back views
  • Expressions
  • Material / costume / prop details
  • Important prop labels, such as handbag, wallet, skateboard, apple basket, scarf, shoes, glasses
  • Identity lock repeated in the prompt
  • A short visual-ID note listing age range, body type, hairstyle, outfit colors, signature props, and do-not-change traits

For stylized 3D animation, keep the character soft, readable, and consistent across later images and videos.

After the main character cards are generated, show a user choice card:

  • Lock character designs and continue (recommended)
  • Regenerate protagonist card
  • Adjust specific visual details
  • Add another character card

Warn the user that changing locked character designs later may require regenerating the shot table, single-shot storyboards, single-shot video clips, assembled main video, and final composite.

STEP 4: Scene Cards

Generate scene reference cards and save them under outputs/ after character cards. Scene cards must show environments only: do not include characters, people, crowd figures, silhouettes, hands, faces, or character cameos. Character action belongs in the shot table, single-shot multi-panel pencil storyboards, and single-shot video clips, not scene cards.

Include:

  • Main environment overview
  • Key light states, such as day / night
  • Emotional sub-spaces
  • Continuity landmarks (fixed objects whose screen position must persist across shots in the same scene, e.g. kitchen island, sofa, door frame, tree, mailbox)
  • Important props in the environment

Then present the numbered options to the user:

  • Lock scene design and continue (recommended)
  • Regenerate scene card
  • Add another scene angle
  • Adjust lighting or layout

STEP 5: Standardized Shot Table Video Prompts (Six Columns)

After character cards and scene cards are locked, output standardized video prompts as a shot information table. This step is mandatory and cannot be swapped with storyboard or video generation.

Required reference: read and follow references/shot-table-spec.md for the exact six-column schema, per-second directive requirements, table-wide rules, user approval card, and mandatory Step 5.5 self-check gate.

Minimum runtime contract:

  • Create a canvas table node named 标准镜头信息表 or standard-shot-table.
  • Use exactly six columns: Shot ID & Duration, Continuity Handoff, Reference Anchors (Spatial + Identity), Hook Type, Shot Description (Per-Second Directives), Audio & Dialogue Track.
  • Every row must include complete per-second directives, continuity handoff, reference anchors, hook type, and audio/dialogue timing.
  • Run the Step 5.5 self-check from references/shot-table-spec.md before storyboarding. Do not enter Step 6 until the self-check passes.

Then show the table approval/self-check choice cards defined in references/shot-table-spec.md.

STEP 6: Text Storyboards Document (Default) + Pencil Image Storyboards (Opt-in)

After the Step 5.5 self-check passes, show a storyboard-mode choice card before producing any storyboard artifact.

Required reference: read and follow references/storyboard-guidelines.md for the default single text storyboards document, optional multi-panel pencil storyboards, shot-level extraction/re-integration, storyboard approval cards, and visualization fallback rules.

Minimum runtime contract:

  • Default mode is one authoritative text storyboards document containing one section per shot.
  • Pencil storyboard images are opt-in visualization artifacts only; they never override the text storyboard.
  • Extract a shot into a standalone text node only when the user flags that shot for heavy iteration.
  • Step 7 must read the matching text storyboard section or extracted standalone node, not the pencil image.

After all storyboards are approved, proceed to the video-model choice card.

STEP 7: Video-Model Choice Card + Single-Shot Video Clips

Before any clip is rendered, show the video-model choice card and resolution choice card.

Required references:

  • Read references/model-selection.md for the H3 default, Seedance 2.0 fallback, per-shot mixed mode, resolution choices, and model-specific prompt shaping.
  • Read references/fallback-policy.md for per-model retry ladders, drift handling, and escalation choices.

Minimum runtime contract:

  • H3 is the recommended default model.
  • Seedance 2.0 is the fallback for high-stakes animation performance or repeated H3 failure.
  • Per-shot mixed mode is allowed only when the shot table marks the model per row; unmarked rows default to H3.
  • Strip all storyboard-only labels before video render.
  • Bind each clip to the approved text storyboard section, exact character cards, and exact scene card.
  • If a clip drifts from the approved Reference Anchors, follow references/fallback-policy.md; do not silently assemble incorrect clips.

After all clips render, place them on canvas in shot order, group them as <title> shot clips, and show the clip approval card defined in references/model-selection.md.

STEP 8: Full Film Assembly, BGM Match, and Final Output

After all single-shot clips are approved, assemble the complete main video, match or generate one continuous BGM track, and produce the final composited video.

Required reference: read references/qc-checklist.md for assembly rules, BGM rules, final review checks, canvas ordering/grouping discipline, user choice-card discipline, and regeneration/latest-asset discipline.

Minimum runtime contract:

  • Preserve the exact shot order from the approved table.
  • Use only approved latest assets.
  • Duck BGM under dialogue, reactions, and important SFX.
  • Do not add subtitles or text unless explicitly requested.
  • Final video must contain no storyboard traces, labels, arrows, timing marks, panel borders, or double-binding labels.

Then run the final review checks from references/qc-checklist.md and deliver the final approved asset.

Boundaries

Do not use this Skill for a single image, a simple edit, a single clip animation, logo design, or pure prompt consultation. If the user only wants a prompt, use a video prompt workflow instead. If the user only wants a character card, use a character breakdown workflow instead.

<!-- QUALITY_BASELINE_V1 -->

When to use(什么时候使用)

当用户需要 为当前请求选择并执行可验证、可恢复的专业工作流 时加载本技能。先从请求中提取目标、输入、约束、交付格式和验收标准;描述摘要为:Create complete stylized 3D animated shorts from a story idea through an ordered production workflow covering project brief, story outline, character and environment cards, standardized shot planning, text or optional pencil storyboards, video-model selection, single-shot generation, assembly, BGM matching, and final review. Use when the user wants an end-to-end narrative animation workflow with strong character consistency, scene continuity, timing, camera, performance, and audio control. Not for single images, simple edits, photorealistic live action, or one standalone clip.。

Rules

  • 先读后写:先确认当前状态与真实能力,再执行会改变外部状态的动作。
  • 权限最小化:只使用完成当前步骤所需的文件、工具、账户与网络范围。
  • 证据优先:运行结果、资源 ID、版本、哈希或测试输出缺失时,明确标记为 NOT_VERIFIED。
  • 幂等优先:保留请求标识与阶段状态;结果不明确时先查询,不进行盲目重试。
  • 隐私安全:日志、示例、回执和错误信息不得包含 token、cookie、密钥或个人敏感数据。

Workflow

Step 1:澄清意图

确认本技能是否匹配目标;若只是相邻需求,交给更精确的技能。

Step 2:执行预检

确认目标、输入、约束、可用工具、成功标准和失败边界;任一关键条件未知时停止在只读阶段。

Step 3:形成计划

列出将调用的工具、会改变的对象、成功标准以及失败后的安全退出方式。

Step 4:执行动作

按最小充分步骤执行,并在关键状态变化处记录证据;每个外部调用均保留可关联的状态或回执。

Step 5:验证交付

输出结果、验证证据、未完成项、风险和明确的下一步,并把事实、推断和未验证项分开陈述。

Validation checklist

  • 技能触发条件与用户意图一致,没有把相邻任务误路由到本技能。
  • 输入、目标对象、版本和输出位置均已明确,且没有使用猜测值替代必填值。
  • 所有写入、付费、发布或不可逆动作都在用户授权范围内。
  • 结果已用独立检查验证;仅有“命令成功”或“文件存在”不算完整验收。
  • 输出包含实际证据、失败/跳过项、剩余风险和可执行的下一步。

Gotchas

  1. 把计划当结果:文档或提示词不等于真实执行;必须标明实际运行层级。
  2. 错误重试:超时或响应丢失可能已经产生远端状态,先查询再决定是否重试。
  3. 隐式扩大范围:批量、全量、发布、覆盖和付费不是普通读写的自然延伸。
  4. 版本漂移:引用外部资源时记录版本、tag 或提交;不要把可变分支当发布证据。
  5. 证据过期:缓存、旧截图和历史测试不能证明当前环境;在交付前刷新关键证据。

不适用与边界

不超出用户给定范围;写入、付费、发布和不可逆动作需要明确授权。 如果请求需要别的技能,不复制其正文;按技能名称进行交接,并保留当前任务上下文。

Progressive disclosure

  • 需要确定输入/输出、状态和授权点时,读取 references/workflow-contract.md。
  • 需要交付前自检时,读取 references/validation-checklist.md。
  • 遇到超时、部分成功或恢复场景时,读取 references/error-recovery.md。
  • 首次运行、拒绝越权和失败恢复分别参考 examples/happy-path.md、examples/boundary-refusal.md、examples/failure-recovery.md。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.