Audio Jingle

Routes audio generation requests to the right backend: Suno or Udio for music beds and jingles, MiniMax or ElevenLabs for voiceover, AudioCraft for sound effects. The workflow is straightforward: reads project metadata to pick the model, assembles a prompt tuned to that provider's format, then calls a unified dispatcher that drops an MP3 into your project folder. The hard constraint is that TTS runs your script verbatim, so you proof it first. Works well when you need a 30 second coffee shop jingle or a product demo voiceover and want to stay inside the Claude context instead of opening three different web UIs.

skills.sh installs: 210
GitHub stars: 106.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add nexu-io/open-design --skill audio-jingle --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly