skills/music-elevenlabs/SKILL.md
Generate background music from text prompts via ElevenLabs Music API. Outputs MP3 files up to 10 minutes. Use for video soundtracks, podcast intros, ambient backgrounds.
npx skillsauth add RonanCodes/ronan-skills music-elevenlabsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate music tracks from text prompts using ElevenLabs' Eleven Music API. Outputs an MP3 file — from a 3-second jingle to a 10-minute background track.
/music-elevenlabs "upbeat electronic dance track with synth leads" [--duration <seconds>] [--output <path>]
/music-elevenlabs "calm ambient piano for a product demo video" --duration 60 --instrumental
/music-elevenlabs --plan composition.json --output soundtrack.mp3
--duration — length in seconds (3–600). Default: 30.--output — output file path. Default: /tmp/music-elevenlabs-<timestamp>.mp3.--instrumental — force instrumental output (no vocals). Default: false.--plan — path to a JSON composition plan for detailed control (mutually exclusive with text prompt).--seed — integer seed for reproducibility (only with --plan).--format — output format. Default: mp3_44100_128.if [ -z "$ELEVENLABS_API_KEY" ]; then
echo "❌ ELEVENLABS_API_KEY not set."
echo ""
echo "Get your key at: https://elevenlabs.io/app/settings/api-keys"
echo "Then set it: export ELEVENLABS_API_KEY=sk_..."
echo "Or add to: ~/.claude/.env"
exit 1
fi
PROMPT="$1"
DURATION_MS=$(( ${DURATION:-30} * 1000 )) # API takes milliseconds
INSTRUMENTAL="${INSTRUMENTAL:-false}"
MODEL="music_v1"
FORMAT="${FORMAT:-mp3_44100_128}"
OUTPUT="${OUTPUT_PATH:-/tmp/music-elevenlabs-$(date +%s).mp3}"
# Validate duration (3s–600s = 3000ms–600000ms)
if [ "$DURATION_MS" -lt 3000 ] || [ "$DURATION_MS" -gt 600000 ]; then
echo "❌ Duration must be between 3 and 600 seconds"
exit 1
fi
--plan)A composition plan gives fine-grained control over sections, tempo, and instrumentation:
{
"sections": [
{
"text": "Gentle piano intro, slow tempo, ambient feel",
"duration_ms": 15000
},
{
"text": "Build energy, add drums and bass, moderate tempo",
"duration_ms": 30000
},
{
"text": "Climax with full orchestra, fast tempo, epic feel",
"duration_ms": 20000
},
{
"text": "Wind down, return to piano, fade out",
"duration_ms": 15000
}
]
}
Section durations: 3000ms–120000ms each. Total: 3000ms–600000ms.
if [ -n "$PLAN_FILE" ]; then
# Composition plan mode
PLAN=$(cat "$PLAN_FILE")
curl -s -X POST "https://api.elevenlabs.io/v1/music?output_format=${FORMAT}" \
-H "xi-api-key: $ELEVENLABS_API_KEY" \
-H "Content-Type: application/json" \
-d "$(python3 -c "
import json
plan = json.loads('''$PLAN''')
data = {
'composition_plan': plan,
'model_id': 'music_v1',
'respect_sections_durations': True
}
print(json.dumps(data))
")" \
--output "$OUTPUT"
else
# Simple prompt mode
curl -s -X POST "https://api.elevenlabs.io/v1/music?output_format=${FORMAT}" \
-H "xi-api-key: $ELEVENLABS_API_KEY" \
-H "Content-Type: application/json" \
-d "$(python3 -c "
import json
data = {
'prompt': '''$PROMPT''',
'music_length_ms': $DURATION_MS,
'model_id': 'music_v1',
'force_instrumental': $INSTRUMENTAL
}
print(json.dumps(data))
")" \
--output "$OUTPUT"
fi
Note: Music generation can take 30–120 seconds for longer tracks. The API streams the response.
if [ ! -f "$OUTPUT" ] || [ "$(wc -c < "$OUTPUT")" -lt 1000 ]; then
echo "❌ Music generation failed. Response:"
cat "$OUTPUT" 2>/dev/null
exit 1
fi
DURATION_ACTUAL=$(ffprobe -v quiet -show_entries format=duration -of csv=p=0 "$OUTPUT" 2>/dev/null | cut -d. -f1)
SIZE=$(wc -c < "$OUTPUT" | tr -d ' ')
✅ Music generated
Prompt: <first 80 chars>...
Model: music_v1
Duration: <N>s
Instrumental: <true|false>
Size: <N> KB
Output: <output path>
Play: open <output path>
# Quick test — generates a 5-second jingle
export $(grep ELEVENLABS_API_KEY ~/.claude/.env)
curl -s -X POST "https://api.elevenlabs.io/v1/music" \
-H "xi-api-key: $ELEVENLABS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt": "short cheerful jingle", "music_length_ms": 5000, "model_id": "music_v1", "force_instrumental": true}' \
--output /tmp/music-test.mp3 && \
echo "✅ API key works" && open /tmp/music-test.mp3
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| ELEVENLABS_API_KEY | yes | — | API key from elevenlabs.io/app/settings/api-keys |
music_v1 is currently the only available model| Use Case | Prompt | Duration | |----------|--------|----------| | Video intro | "cinematic orchestral buildup, epic and inspiring" | 10s | | Podcast intro | "warm jazzy lo-fi beat with soft piano" | 15s | | Product demo | "clean modern corporate background, upbeat but subtle" | 60s | | Tutorial | "calm ambient electronic, minimal and focused" | 120s | | Trailer | "dark dramatic tension building to explosive climax" | 30s | | Outro | "gentle acoustic guitar fade out, peaceful" | 10s |
generate-video — background music for Remotion video compositionssfx-elevenlabs — layer SFX over music for full audio designtts-elevenlabs — combine narration with background musicaudio-mix — mix voice + music + SFX into a final audio trackdevelopment
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
devops
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
development
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
development
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h