Music Generator Skill (Full SOP)

Capability Overview

This skill supports the following intents: 1) Generate a full song with lyrics 2) Generate pure background music (BGM) 3) Generate lyrics only (no audio) 4) Query music generation task status

Users can describe the music they want in plain language. The system auto-determines the mode and handles parameter inference and task tracking.

Triggers and Natural Language Examples

The following natural language requests will trigger this skill: - Generate a romantic love song - Write lyrics about the night sky - Create electronic music suitable for short‑video background - Check my music generation progress - I want a cheerful background music track

Execution (SOP Step‑by‑Step)

Preflight Check (Mandatory)

• Read MUSICFUL_API_KEY from the skill folder’s .env (resolved at runtime via the running script path): /.env
• If not configured (empty/missing), immediately inform the user:
  • "MUSICFUL_API_KEY is not configured. Please visit https://www.musicful.ai/api/authentication/interface-key/ to obtain/purchase an interface key, then write the KEY into /.env under MUSICFUL_API_KEY."
• Stop subsequent calls and wait for the user to complete configuration before continuing.

The execution flow is intent‑based and incorporates a two‑stage return and a "lyrics‑first" UX: - Single command entry: /music_generator, with mode branch control: - mode=normal (default): generate and show lyrics → submit generation → return preview (status=2) → return final (status=0) - mode=bgm: pure music (instrumental=1), no lyrics → preview first → then final - mode=lyrics: return lyrics text immediately - When using the "custom lyrics" path (built into the normal flow or future extensions): submit generation directly and poll (preview first, then final)

Scenario A: Generate a Full Song with Lyrics

Typical user inputs: - Generate a romantic electronic song - Write a sad rock song and generate audio - Here are some lyrics, please use them to create the song: [...user‑provided lyrics...]

Detailed Flow

Step 1: Intent Recognition - If the user provides complete lyrics, treat it as lyrics‑provided generation; - Otherwise, assume lyrics need to be generated automatically and then used to synthesize the song.

Step 2: Lyrics Handling - If lyrics are provided → use them directly; - If not provided → call the V1 Lyrics API to generate lyrics content;

Step 3: Submit Music Generation Task - POST {BASE_URL}/v1/music/generate - body: { action: "custom", lyrics: "<lyrics>", style: "<inferred from user>", mv: "<default to latest high‑quality model>" }

Step 4: Automatic Task Polling (Two Stages) - GET {BASE_URL}/v1/music/tasks?ids= - Status semantics (key): - status = 2 → preview stage complete (returns audio_url as preview link) - status = 0 → full audio complete (returns audio_url as downloadable final link) - others → processing or failed (use fail_code/fail_reason) - Polling strategy: 1) On first status=2: immediately announce "preview is ready" and return audio_url for listening; 2) Continue polling until status=0: then return "final audio is ready" with audio_url (download/publish).

Step 5: Return Results to the User (Two‑Stage × Two Songs) - The system by default generates two songs/two task_ids (e.g., ids=[id1,id2]). For each id, perform the two‑stage return independently: - Stage 1: when this id reaches status=2 → return the preview link (audio_url) - Stage 2: keep polling this id → when status=0 → return the full mp3 download link (audio_url) - Recommended output format (one block per song): - title: