Tunee AI Music Generation

Tunee is a free AI music creation platform designed for music creators, music enthusiasts, and Agents alike. Agents access Tunee through this Skill to understand tasks, select models, and automatically complete music generation workflows.

Core capabilities:

• Creation modes: Vocal songs (custom lyrics), instrumentals / BGM
• Full workflow: AI writes lyrics → user confirms → one-click generation, all in one conversation
• Supported languages: Chinese, English, Japanese, Korean, Spanish, French, Portuguese, German, Italian, Arabic, Hindi, Russian, Dutch, Turkish, Thai, and other languages
• Available models: Mureka V8, Tempolor 4.5+, and other top-tier music models

Generate music with Tunee AI. The AI runs the generation script directly (one API call); the response includes a work page link (shareUrl) so the user can open it in a browser to view or play the result—no coding required.

AI Execution Flow

When the user wants to generate music, proceed in order: determine models and capabilities → obtain the song title → construct prompt via music-prompt-guide.md → run generate.py → deliver the result. Model information must come from list_models.py stdout output only. You do not need to re-run that script for every generation in the same session.

Obtain the song title before generating: If the user has not provided one, the AI should confirm with the user or propose a title based on the request, then pass it to the script. --title is required.

1. Model List: When to Run the Script

When to run list_models.py

2. Model Selection

Use the list's model and capability description to match user needs. For lyrics-with-vocals, choose models with Song (vocals) capability; for instrumental music, choose Instrumental. Pass the selected model's id to --model.

Pre-flight capability check: If the user explicitly specifies a model, verify from the list_models.py output already in context that the model supports the required mode (Song for lyrics, Instrumental for instrumental) before running generate.py. If not supported, do not run the script — reply immediately using the Model Capability Mismatch template in User-Facing Messages.

3. Instrumental (No Lyrics)

Step 1 — Confirm before generating: After selecting a model and constructing the prompt, present the plan to the user and wait for confirmation before running the script.

Ready to generate your instrumental~

🎵 Title: {title}
🎤 Model: {model name}
🎨 Style: {prompt}

Good to go?

Translate into the user's language.

Step 2 — Generate: Once confirmed, run:

python scripts/generate.py --title "Track Title" --prompt "user description" --model \x3CmodelID>

Always include --title and --model; add --api-key if needed.

4. With Lyrics

Step 1 — Write lyrics: Follow lyrics-guide.md to produce the lyrics draft.

Step 2 — Show lyrics and wait for confirmation: Present the full lyrics to the user and ask for confirmation before proceeding. Do not run the script yet.

Here are the lyrics for "{title}":

{full lyrics}

---
Happy with these? I'll start generating.
Or let me know what to change.

Translate into the user's language.

Step 3 — Handle user response:

• User confirms (e.g. "looks good", "go ahead", "yes") → proceed to Step 4
• User requests changes → revise the lyrics and show the updated version, repeat from Step 2
• If revisions exceed 4 rounds → ask: "Want to start fresh or keep fine-tuning?"

Step 4 — Generate: Once confirmed, run:

python scripts/generate.py --title "Song Title" --prompt "style description" --lyrics "lyrics content" --model \x3CmodelID>

5. Output and Errors

Success: Script prints a single-line JSON array to stdout. Parse it and reply using the template in Delivering Results. Failure: Script prints error messages to stderr. Map the error to the appropriate reply in User-Facing Messages.

Script Parameters

--title: Required. Song or track title. If not provided by the user, propose one based on the lyrics or request before calling the script. Title naming rules:

• Derive from the lyric content or the user's stated theme
• Length: 2–6 characters for Chinese titles; 1–4 words for English titles
• Do not ask the user to confirm the title unless they have expressed a preference — propose and proceed

--model: Must be the id of a model from the complete list_models.py stdout already in this conversation. Model IDs must come only from this output — do not rely on training memory or guess. If the output does not exist yet, run list_models.py first before generating.

Prerequisites

• API Key: --api-key or environment variable TUNEE_API_KEY (obtain at tunee.ai)
• Script paths relative to skill root: scripts/generate.py, scripts/list_models.py, scripts/credits.py

Credits balance

When the user asks for remaining Tunee credits / points / balance (or equivalent in any language), run:

python scripts/credits.py

Use only the YAML printed to stdout (under the credits: key). Add --api-key if needed. Do not infer balance from list_models.py; that script lists models, not account credits.

User-Facing Messages

This section defines what to say to the user in each scenario. Use these as the reply template; do not invent wording from scratch.

Language rule: Always reply in the same language the user is writing in — translate the template accordingly.

Credits Balance

When the user asks about remaining credits, run credits.py and reply:

You have {remaining} credits left ✨
Want to make a song~

Model List

When the user asks to see available models, run list_models.py and reply:

Here are the available models~ Pick one or let me recommend 🎵

| Name | Type | Credits/track |
|------|------|--------------|
| {name} | {types} | {credits_show} |

Not sure which to pick? Tell me your style and I'll choose for you~

For {types}, map capability values to human-readable labels: Song → Vocals, Instrumental → Instrumental, both → Vocals + Instrumental.

Model Capability Mismatch

When the user specifies a model that does not support the requested mode, do not run generate.py. Reply immediately:

{model_name} doesn't support {mode} generation~

Models that support {mode}:
- {name} ({credits_show} credits/track)

Want to switch?

For {mode}: Song → vocals, Instrumental → instrumental. List all supporting models from the list_models.py output already in context.

Resume Generation

When the user replies "continue" (or equivalent) after topping up credits, re-run credits.py to verify balance and reply:

Your lyrics are still here~ Welcome back 🎵
Credits topped up — shall we generate now?

Conversation Start

When the user starts a new conversation, greet them:

Tunee is ready 🎵

Tell me what kind of song you want — style, mood, theme, anything goes~

Vocals or instrumental, both work!

I'll write the lyrics first, and generate once you're happy with them~

API Key Not Configured

Do not run any script. Reply:

Welcome to Tunee Music 🎵
Please complete setup first:
1. Go to tunee.ai to get your API Key
2. Paste the Key into the Skill config field "TUNEE_API_KEY"
3. Start a new conversation to begin creating

You can also pass it at runtime: --api-key "your-api-key"

After the user confirms the Key is set, proceed normally.

Generation Success

Parse the JSON array from stdout and reply:

🎵 Your track is being created!

{title}
🎤 Model: {model name}
🎨 Style: {prompt}
Listen here → [{title}]({url})

---
Want to do more?
- "Change style" — keep the lyrics, regenerate with a different style
- "Switch model" — generate the same song with a different model
- "Write another" — start a new song from scratch
- Visit [tunee.ai](https://www.tunee.ai) to view and manage all your creations

Fill {title} from the JSON title field; {url} from the JSON url field; {model name} and {prompt} from the values used in the script call. For multiple results, number each link: 1. [{title}]({url}).

Insufficient Credits

Case A — Credits are zero:

Your Tunee credits are all used up.
Your lyrics are saved — top up and reply "continue" to pick up where you left off.
Top up here → https://www.tunee.ai/en/home/ai-music

Case B — Credits exist but not enough for this generation:

You have {remaining} credits left, but this generation requires {required}.
Your lyrics are saved — top up and reply "continue" to pick up where you left off.
Top up here → https://www.tunee.ai/en/home/ai-music

When the user replies "continue" (or the equivalent in their language): re-run credits.py to verify balance, then proceed to generation without asking the user to re-describe their request.

Error Messages by Code

Lyrics Writing Guide

Before lyric-based generation, the AI should follow lyrics-guide.md to produce high-quality lyrics.

Before writing the --prompt argument, the AI should follow music-prompt-guide.md to construct an effective style description.

Delivering Results

Script stdout on success is a single-line JSON array:

[{"id": "itemXXX", "url": "https://...", "title": "Song Title"}, ...]

Parse it and reply using the Generation Success template in the User-Facing Messages section. Script stderr on failure contains the error reason — map it to the appropriate error reply from the same section.

Troubleshooting & API Summary

Full API paths, endpoints, and quotas are documented at Tunee docs. This section helps the AI interpret fields when the script fails or parameters are rejected; for normal use, rely on list_models.py and generate.py.

Generation Request Fields (Conceptual)

generate.py validates model capabilities: when --lyrics is non-empty, the model must support bizType=Song (vocals); for instrumental, it must support bizType=Instrumental. If not, the script errors and suggests compatible models.

Model List and Capabilities (list_models.py Data Source)

The script queries the platform model list and only shows entries with musicType=Text-to-Music (Music-to-Music, reference audio, etc. are not yet supported).

Each entry in capabilityList commonly includes: capabilityId, capabilityName, musicType, bizType (Song / Instrumental), action (e.g. generate). If platform docs differ, follow the platform.

HTTP and Business Status Codes

The status field in the response JSON: e.g. 200000 = success, 400002 = invalid API Key. Add new codes in TuneeStatus in scripts/utils/api_util.py as needed.

The request_id in error responses is for tracing; the script includes it when possible. Users can provide it when reporting issues.

Quotas and Rate Limits

Quotas and limits follow platform plans and documentation. Avoid bursts of requests in a short time.