mm3-captioning

Formats Structured Captions for MiniMax-Music3 music generation prompts.

151|22|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/scragnog/HOT-Step-CPP --skill mm3-captioning-scragnog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mm3-captioning
Source: https://github.com/scragnog/HOT-Step-CPP/tree/main/.claude/skills/mm3-captioning
Command: npx skills add https://github.com/scragnog/HOT-Step-CPP --skill mm3-captioning-scragnog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? MiniMax-Music3 generations drift genre and ignore instructions when given short free-text prompts, because the model was trained on a specific three-section Structured Caption format that most prompt-assembly code does not emit. ## Core Features & Use Cases - Structured Caption contract: Documents the mandatory Global Metadata, Vocal Details, and Arrangement sections, the 5,000-token budget shared with lyrics, and the rule that lyrics never enter the caption. - Vendored upstream reference library: Ships MiniMax's official captioning skill with a genre router, 18 family indexes, and 1,000 example templates for progressive-disclosure retrieval. - Empirical tuning notes: Records ear-verified A/B results on caption dialect, genre slash-pairs, Basic Attributes correction via Essentia, and caption-lyrics pairing effects on song endings. - Use Case: When building the request-translator that turns Lyric Studio output into an MM3 prompt, use this Skill to emit plain-text section labels inside the <|caption_start|> slot instead of markdown or a one-line description. ## Quick Start Read the vendored upstream SKILL.md and genre router, then write a three-section Structured Caption for my MM3 generation request about an energetic pop-punk track.

Frequently Asked Questions about mm3-captioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a caption for MiniMax-Music3 music generation?

Write a Structured Caption with three plain-text sections in order: Global Metadata, Vocal Details, and Arrangement. Keep it under the 5,000-token budget shared with lyrics, and never quote or paraphrase lyric text inside the caption.

Why does MiniMax-Music3 ignore my prompt or drift genre across seeds?

Short one-line captions produce high take-variance and genre drift in MM3. Detailed three-section Structured Captions are the adherence lever, and the prose vocabulary must match the target genre family's dialect in the upstream templates, not just name the genre.

Should MM3 captions use markdown headings or plain text labels?

Use plain-text section labels like Global Metadata, Vocal Details, and Arrangement with no markdown syntax. The reference templates and the tokenizer's caption slot treat the caption as an opaque string, and the trained format uses plain labels.

Can I convert an existing ACE-Step caption into MM3 format?

Mechanical restructuring of ACE captions consistently underperforms hand-written Structured Captions in ear-judged tests, even when the content is rich. The reliable path is captioning from the audio directly in MM3 format, for example with ace-caption --mode mm3.

How do I keep BPM and key accurate in an MM3 caption?

Captioning models are unreliable on tempo and key, so rebuild the Basic Attributes line deterministically from measured values such as Essentia bpm, keyscale, and time signature. Preserve the model-written genre clause, since genre judgment is where the model performs better.

What are the limitations of spectral metrics for judging caption quality?

Spectral proxies like flatness, centroid, and intro ratio repeatedly mislead when evaluating caption changes, because genre arrival itself shifts those numbers. Caption adherence for MM3 must be judged by ear across multiple seeds.