beatra-ai/beatra-skills / plugins/suno-lyrics-to-song/skills/suno-lyrics-to-song
suno-lyrics-to-song
VerifiedTurn 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.0 KB |
| agents/openai.yaml | config | 481 B |
| assets/icon.png | binary | 11.4 KB |
| assets/icon.svg | other | 927 B |
| install-source.json | config | 39 B |
| manifest.json | config | 4.8 KB |
| references/billing-errors-and-recovery.md | markdown | 5.8 KB |
| references/installation-and-auth.md | markdown | 9.3 KB |
| references/installation-registration.md | markdown | 2.0 KB |
| references/lyrics-intake-and-modes.md | markdown | 3.3 KB |
| references/mcp-connection.md | markdown | 3.3 KB |
| references/music-editing-and-audio.md | markdown | 21.3 KB |
| references/review-and-recovery.md | markdown | 3.6 KB |
| references/song-direction-and-request.md | markdown | 3.0 KB |
| references/tasks-and-results.md | markdown | 2.2 KB |
| references/uninstall-and-disconnect.md | markdown | 2.7 KB |
| references/updates-and-security.md | markdown | 5.9 KB |
| references/workflow.md | markdown | 4.2 KB |
| scripts/authorize.py | script | 61.1 KB |
| scripts/mcp_client.py | script | 86.4 KB |
| scripts/uninstall.py | script | 12.6 KB |
references/lyrics-intake-and-modes.md
View on GitHub# Lyrics intake and modes
## Accepted starting material
The starting point must be lyric material already supplied by the user or already
visible in the conversation:
- complete existing lyrics;
- a verse, chorus, or other lyric draft;
- loose lines intended as lyrics;
- an existing hook that needs supporting structure.
When the user brings only a topic, mood, story brief, or title, ask them for one lyric
line or hook to anchor this lyrics-to-song workflow. That is the only missing creative
input required before work can begin.
## Preserve mode
Use Preserve by default when the user asks to arrange, compose, generate, or make a
song from supplied lyrics without asking to change the lyric text. Do not interrupt
the workflow with a Preserve-or-Optimize question.
Treat each supplied lyric line as an immutable unit.
- Preserve every character, punctuation mark, spelling choice, capitalization choice,
and whitespace within each lyric line.
- Preserve every complete lyric line and its exact position in the supplied line
sequence; do not split, merge, paraphrase, correct, shorten, add, or reorder
lyric-body text.
- Only adjust surrounding line breaks or blank-line spacing to mark section
boundaries. Never use this formatting permission to change any complete lyric
line's content or order.
- Add section labels such as `[Verse]`, `[Chorus]`, or `[Bridge]` only outside the
lyric-body lines. Labels are arrangement instructions, not new lyrics.
- When a refrain should repeat, include the repeated lines in the complete proposed
version so the final production confirmation covers the exact lyric text.
Before confirmation, state whether surrounding line breaks or blank-line spacing were
adjusted and show the complete result so the user can compare it with the source.
## Optimize mode
A request to polish, rewrite, improve, or optimize grants permission to change the
lyric text. Otherwise remain in Preserve. Then optimize only what serves singability
and the intended song:
- balance line length and breath load;
- align natural word stress with rhythmic emphasis;
- remove awkward phrasing without changing intended meaning;
- strengthen rhythmic flow, rhyme, repetition, and recall;
- sharpen the hook and section contrast;
- shape verses, chorus, and bridge around one emotional progression.
Record every must-keep line before editing and preserve each one exactly, including its
characters and punctuation. Names, facts, quotations, and identity-sensitive wording
also remain fixed when the user marks them as fixed. If a must-keep line creates a
singability tradeoff, explain it rather than silently changing it.
Show the full revised lyric, not excerpts, and summarize material changes inside the
complete production card. Approval of that complete card both accepts the lyric and
authorizes one paid generation. When the user explicitly asks to review the lyric
first or says not to spend yet, show the revised lyric separately and stop before any
paid call.
## Structure checks
For either mode, confirm that the selected section order supports a clear emotional
arc; the hook arrives deliberately; repeated material has a purpose; line density is
plausible for the tempo feel; and labels stay short and conventional. Do not claim
that a written structure guarantees exact pronunciation, melody, duration, or casting.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |