Skip to content

beatra-ai/beatra-skills / plugins/suno-lyrics-to-song/skills/suno-lyrics-to-song

suno-lyrics-to-song

Verified

Turn complete lyrics, a rough lyric draft, loose lines, or an existing hook into a structured, listenable Suno song. This Suno lyrics-to-song workflow works as an AI song generator from lyrics and AI music generator from lyrics: choose Preserve mode to keep every original line or Refine mode to improve rhythm, rhyme, singability, and hook strength. Build the song structure across verses, chorus, bridge, and purposeful repetition, then create a style prompt for music with genre, mood, arrangement, and vocal direction for Suno custom lyrics. Use it to turn lyrics into a song, make a song from lyrics, convert lyrics to music, get help from a lyrics songwriting assistant, or take rough lyrics to song-ready form through a custom lyrics-to-song process.

references/workflow.md

View on GitHub
# Workflow

## 1. Qualify the source

Begin when the conversation contains existing lyrics, a lyric draft, loose lyric
lines, or an existing hook. Reuse visible context. If the user provides only a topic,
story idea, or creative brief, ask for one lyric line or hook; no other creative input
is mandatory before the workflow can begin.

Capture the lyric source verbatim before editing. Identify the language and register,
the strongest existing hook, declared must-keep lines, names or facts that cannot
change, and whether the text is complete or fragmentary.

## 2. Choose the edit contract

Reuse a clear Preserve or Optimize intent from the request. A request to polish,
rewrite, improve, or optimize grants editing permission. A request to arrange,
compose, generate, or make a song from supplied lyrics defaults to Preserve without a
mode question. Apply [lyrics intake and modes](lyrics-intake-and-modes.md), show
meaningful Optimize changes, and retain the original source for comparison.

## 3. Structure and direct the song

Arrange the accepted material into purposeful sections such as verse, pre-chorus,
chorus, bridge, or outro. Infer a useful title and musical direction from the lyrics,
covering style, mood, tempo feel, instrumentation, arrangement arc, section contrast,
lead-vocal treatment, and exclusions. Ask only when an unknown choice materially
changes the lyric or paid payload.

Before that card, call `beatra.models.list` with `{"capability":"text_to_music"}`
and read the `suno-6` entry's `pricing`. Show one final production card
containing:

1. the complete lyric text, including section labels;
2. the title;
3. the complete music direction;
4. any single-lead gender field that will be used;
5. `suno-6`, relevant options, and the fact that approval starts the paid calls listed on the card;
6. Work — one Suno song from the approved lyrics, a `beatra.music.generate` call, plus any finishing step the user asked for with it;
7. Credits — the live `suno-6` price just read, per slot and in total, with each finishing step as its own line at its live `audio_process` price, the total including every line, never a remembered number;
8. Count — one paid call for this song, plus one per finishing line on the card;
9. Identity — one new opaque `client_request_id` per line on the card; a changed lyric, title, direction, model, or option mints a new ID;
10. If we stop here — the structured lyrics remain usable;
11. If the balance is insufficient — relay the official message and its top-up URL exactly.

A clear approval of this complete card accepts any shown Optimize changes and
authorizes the paid step. Do not ask for another confirmation or require a separate
“generate audio” command afterward. If the user explicitly asks to review lyrics first
or says not to spend, show the draft but stop before paid execution; prepare the final
card only when they are ready to consider generation.

## 4. Freeze and submit once

Validate every field against [song direction and request](song-direction-and-request.md).
After the complete production card is approved, create one opaque 1..128-character
`client_request_id`, retain an exact copy of every generation field, and call
`beatra.music.generate` exactly once through the bundled `scripts/mcp_client.py`.

When the response includes a `task_id`, store it and use only `beatra.tasks.get` for
that task. Do not submit a replacement while it is queued or running.

## 5. Deliver or recover

Use [review and recovery](review-and-recovery.md) for polling, a lost task ID,
uncertain delivery, cancellation, terminal failure, and result review. Stop active
polling after 30 minutes if the task remains nonterminal, report the current factual
state, and explain how to resume the same task later.

Any revised lyrics, title, music direction, model, or model option define a new paid
request. Show the changed complete lyrics and direction, obtain new generation
confirmation, and create a new request identity. When only one part of the chosen
song needs to change and this account has the music tools, use `replace_section`
instead of a new song, and `extend` to continue it; each is its own confirmed
call and never runs automatically or repeatedly (see
[music editing and audio](music-editing-and-audio.md)).
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall