Audio Jingle
Audio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Audio Jingle when an AI agent needs a reusable SKILL.md workflow for this job: Audio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
When not to use it
Skip Audio Jingle when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/audio-jingle # Save SKILL.md to ~/.claude/skills/audio-jingle/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/audio-jingle/SKILL.md. For a shared project, commit the folder at .claude/skills/audio-jingle/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Audio Jingle skill for this task: Use Audio Jingle when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Audio Jingle Skill
Three sub-modes. The active project's `audioKind` decides which one runs:
| `audioKind` | Models we route to | Plan focus | |---|---|---| | `music` | Suno V5 (default), Udio, Lyria 2 | genre + tempo + instrumentation | | `speech` | MiniMax TTS (default), Fish, ElevenLabs V3 | script + voice + pacing | | `sfx` | ElevenLabs SFX (default), AudioCraft | texture + impact + duration |
## Resource map
``` audio-jingle/ ├── SKILL.md └── example.html ```
## Workflow
### Step 0 — Read the project metadata
`audioKind`, `audioModel`, `audioDuration` (seconds), and (for speech) `voice`. Branch by known values and use them verbatim. Missing metadata is not an instruction to ask: infer a safe default when possible, and emit a clarifying form only when the missing answer would materially change the requested output or prevent generation.
Important: `voice` is provider-specific. For `minimax-tts`, `--voice` must be a valid MiniMax `voice_id` (for example `male-qn-qingse`), not a natural-language description. If you only have a prose voice brief ("warm female narrator", "neutral Mandarin"), keep that in your plan but omit `--voice` so the daemon's default voice id applies, or ask the user to choose a specific id.
### Step 1 — Plan
**Music** - Genre + reference artists (1-2) - Tempo (BPM) + key - Instrumentation (3-5 instruments max) - Vocals: yes / no / hummed / choir - Mood arc (intro → chorus → outro)
**Speech** - Script (final, not draft — TTS runs verbatim) - Voice target + pacing For MiniMax this means a real `voice_id`, not prose in `--voice` - Pronunciation hints for proper nouns / acronyms
**SFX** - Texture (impact / whoosh / ambience / foley) - Duration + envelope (sharp attack vs. gentle swell) - Layering note (single hit vs. stacked)
State the plan in 2-3 sentences before dispatching.
### Step 2 — Compose the prompt
Use the format the upstream model prefers. Bind `audioDuration` to the API parameter directly; never put "make it 30 seconds" in prose.
### Step 3 — Dispatch via the media contract
Use the unified dispatcher — do **not** call provider APIs by hand:
```bash "$OD_NODE_BIN" "$OD_BIN" media generate \ --project "$OD_PROJECT_ID" \ --surface audio \ --audio-kind "<music|speech|sfx>" \ --model "<audioModel from metadata>" \ --duration <audioDuration seconds> \ [--voice "<provider voice id (speech only)>"] \ --output "<short-slug>-<duration>s.mp3" \ --prompt "<assembled prompt from Step 2 — for speech, the literal script>" ```
The command prints one line of JSON: `{"file": {"name": "...", ...}}`. The bytes land in the project; the FileViewer renders the audio transport controls automatically.
### Step 4 — Hand off
Reply with: plan summary, the filename returned by the dispatcher, and one sentence on what to try if the user wants a variation (e.g. "swap tempo from 92 to 108 BPM" rather than "make it different").
## Hard rules
- TTS runs your script **literally**. Proof it before dispatching — even one stray comma changes the cadence. - MiniMax TTS rejects free-form voice prose in `--voice`. Use a real MiniMax `voice_id` (for example `male-qn-qingse`) or omit the flag and let the daemon's default voice apply. - Music: under 30s = single section; 30–90s = intro + body; 90s+ = full arc. Don't try to fit a 3-act song into 15 seconds. - SFX: prefer one well-described layer over a paragraph of "make it cool" — generators reward specific texture words. - Save the file every turn. The audio viewer shows transport controls the moment the file lands.
Intended uses
- Use Audio Jingle when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.