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/billing-errors-and-recovery.md
View on GitHub# Billing, errors, and recovery
Every generation tool consumes Beatra credits and creates an asynchronous task.
Use one logical request identity across transport uncertainty so recovery cannot
accidentally create or charge a duplicate task.
## Submit a billable request
1. Assemble the final generation arguments.
2. Generate one opaque `client_request_id`.
3. Submit exactly once.
4. Store both `client_request_id` and the returned `task_id`.
5. Poll with `beatra.tasks.get`; do not resubmit while the task is queued or
running.
The prepaid amount accepted with the request can be an estimate. A successful
task is settled against authoritative measured usage. Read the terminal
`usage` and `billing` fields, and report net credits as
`billing.net_charged_credits`. Do not promise that the initial estimate
is the final charge.
## Run a batch
When one request becomes many paid calls (a list of items, a loop, or a
script):
1. Before the first paid call, price the whole batch from the live prices
(`beatra.models.list`, or `beatra.social.tools.get` for social data) and
tell the user the estimated total.
2. Let the first `insufficient_balance` stop the whole batch. Do not go on to
the next item; report which items finished and which did not.
3. Resume only the unfinished items, and only after the user says they have
topped up. A refused item keeps its `client_request_id` and arguments.
## Recover an uncertain response
- If no response arrived, make an identical retry with the same
`client_request_id` and exactly the same generation arguments.
- If any prompt, input artifact, model, output setting, or other generation
argument changes, treat it as new work and use a new `client_request_id`.
- If the task ID was lost, use `beatra.tasks.list` before considering a retry.
- If remote execution failed, report the terminal error. Start changed or newly
requested work only with a new request ID.
## Handle structured failures
- HTTP 401 authentication failure: do not replay the paid call automatically.
Run `python3 scripts/authorize.py` and follow its output
until it prints `Beatra is ready`, then recover with the original request
identity and unchanged arguments.
- Timeout, DNS/TLS, HTTP 429, HTTP 5xx, or another transport failure: preserve
the credential. If delivery of a paid call is uncertain, retry only with the
same `client_request_id` and exactly the same arguments after connectivity
recovers.
- Insufficient scope: explain that the active connection lacks required access;
run `python3 scripts/authorize.py --force` only after the
user explicitly chooses to reconnect the full Beatra authorization. Never ask
for a media-specific grant.
- Insufficient balance (error code `insufficient_balance`): relay the returned
message to the user — it already carries the facts that matter: nothing was
charged, the top-up link, credits take effect immediately, and the same
request can be retried as-is. Translate into the user's language but keep
the URL exactly as returned. Stop all remaining paid work, including the
rest of a batch, and do not retry until the user says they have topped up.
A successful task can also leave a negative balance when actual measured
usage exceeded the estimate; the output remains valid, but new billable
work must wait for a top-up.
- After that refusal, `scripts/mcp_client.py` holds further calls to the same
tool on this computer: it answers them with the same message and sends
nothing (`details.local_hold`). Its `details.agent_note` names the balance
check that lifts the hold once the user says they have topped up. If the user
chose a cheaper request instead, run that cheaper call once with
`--recheck-balance`. Never put `--recheck-balance` in a loop or script.
- Some refusals also name another way forward (`details.recovery.alternative`;
the message states it in words). Relay it in the message's words with the
top-up option and do not call again on your own. Choosing it is new work, not
a retry: submit the request it describes once, with a new
`client_request_id`; `charges_now_credits` is what that submission charges.
When it is 0, the user's choice is the approval; above 0, show a card with
that price first.
Choosing it replaces the refused request: drop that request and its
`client_request_id`, never replay it after a later top-up, and continue from
the new request's result.
When its result waits for the user (for example a voice with status
`pending_activation` and its activation price), present the result and its
price, and continue only after the user agrees. This applies even where a
production card's balance line says only to wait for a top-up. The bundled
client does not hold the tool after a refusal that carries `details.offer`,
such as the free voice preview.
- Idempotency conflict: the request identity was reused with different
arguments. Do not retry it. Keep the original task if it exists, or use a new
`client_request_id` only for user-approved changed work.
- Rate or concurrency limit: honor the returned retry delay, then retry the
exact same arguments with the same request identity. Do not create a
replacement task.
- Validation failure or model incompatibility: call `beatra.models.list` for current
constraints, correct the invalid arguments, and use a new
`client_request_id` because the generation inputs changed.
- Upload expiration, MIME mismatch, or byte-length mismatch: request a fresh
grant and upload the unchanged file again. Never reuse a consumed or expired
grant.
- Remote execution failure: preserve the Beatra error code and task ID;
report only the failure classification and billing/refund fields returned by
Beatra. Do not infer a different cause or promise a refund that is not shown.
Never expose authentication tokens, complete private prompts, or sensitive
input content while explaining recovery.
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 |