agentleFS
Sign inStart free
SwotAtmkSwotAtmk/infinite-creation/skills/h3-prompt-writing/SKILL.md

h3-prompt-writing

Skill56 starsChanged 47 days agoMITView on GitHub

Write MiniMax H3 video generation prompts for T2VA, I2VA, FL2VA, L2VA, and Ref2VA. Use when rewriting multimodal requests into H3 prompt structures, composing integrated_multimodal_description, overall_soundscape, and non_diegetic_music, aligning keyframes, or defining reference labels for images, videos, and audio.

11 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 2 are common, 3 are distinctive, and 4 are very specific to this project.

  • 2

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the model supports image input, view each unique character/scene/prop reference image ONCE via view_asset and reuse it across shots — do …

    line 12
  2. Very specific:

    Use integrated_multimodal_description, overall_soundscape, and non_diegetic_music in the order shown in references/base-en.txt.

    line 24
  3. Very specific:

    Read references/ref-en.txt for label rules, retention analysis, and complete examples.

    line 30
  4. Common:

    Write rewrite sections in English.

    line 34
  5. Common:

    Avoid plot summaries, unresolved reference labels, and timing that does not match the requested duration.

    line 36
  6. Distinctive:

    Always match the total duration of the description to the requested video length (2–15 seconds), driven by content rhythm: a single short …

    line 38
  7. Very specific:

    Keep reference labels consistent (e.g.

    line 39
  8. Distinctive:

    Prefer concrete visual and audio details over abstract words like "cinematic" or "beautiful".

    line 40
  9. Distinctive:

    When using keyframes (I2VA / FL2VA / L2VA), clearly state how the first and/or last frame connects to the timeline.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 10 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

H3 Prompt Writing

Workflow

  1. Identify the input mode: T2VA, I2VA, FL2VA, L2VA, or full-reference Ref2VA.
    • If the model supports image input, view each unique character/scene/prop reference image ONCE via view_asset and reuse it across shots — do NOT re-view the same image per shot; use view_shot_references(shot_id) only when a shot introduces an asset you have not yet seen.
  2. For base text/keyframe modes, read references/base-en.txt and follow its final prompt structure.
  3. For full-reference mode, read references/ref-en.txt and follow its six-section rewrite format.
  4. Preserve the exact field names, section order, labels, and timing notation from the selected guide.

Base Modes

  • T2VA: build the full audiovisual timeline from text.
  • I2VA: start from the first frame and develop forward from it.
  • FL2VA: describe the continuous path between the first and last frames.
  • L2VA: infer a plausible opening and converge to the supplied last frame.

Use integrated_multimodal_description, overall_soundscape, and non_diegetic_music in the order shown in references/base-en.txt.

Full-Reference Mode

Ref2VA rewrites use subject_definitions, summary, retention_analysis, detailed_description, overall_soundscape, and non_diegetic_music in that order. Reference labels stay consistent across all sections.

Read references/ref-en.txt for label rules, retention analysis, and complete examples.

Output Rules

  • Write rewrite sections in English; preserve dialogue, lyrics, and visible scene text in their original language.
  • Describe each shot by composition, subjects, environment, actions, camera, sound, and the exact point where referenced content appears.
  • Avoid plot summaries, unresolved reference labels, and timing that does not match the requested duration.

Tips for Better Results

  • Always match the total duration of the description to the requested video length (2–15 seconds), driven by content rhythm: a single short line of dialogue needs only 2–4 seconds — do not pad short shots to 10+ seconds.
  • Keep reference labels consistent (e.g. <Picture 1>, <Video 1>, <Audio 1>) across every section.
  • Prefer concrete visual and audio details over abstract words like "cinematic" or "beautiful".
  • When using keyframes (I2VA / FL2VA / L2VA), clearly state how the first and/or last frame connects to the timeline.

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.

Check your setup, free