Skip to content

coroboros/agent-skills / skills/suno-produce

suno-produce

Verified

Create and revise Suno v5.5 prompt artifacts from a song, track or album brief. Produces TRACK.md, ALBUM.md for explicit multi-track work, and optional ARTIST.md identity. Validates prompt fields and preserves supplied lyrics. Artifact-only; audio generation stays in Suno. Pure lyric writing and audio post-production use other skills.

FileKindSize
SKILL.mdskill md18.8 KB
evals/evals.jsonconfig3.7 KB
references/genre-templates.mdmarkdown9.7 KB
references/rights-and-deprecation.mdmarkdown7.6 KB
references/sliders-and-personalization.mdmarkdown9.2 KB
references/songwriting-craft.mdmarkdown5.3 KB
references/style-and-lyrics.mdmarkdown18.6 KB
references/track-schema.mdmarkdown15.2 KB
scripts/validate.pyexecutablescript37.0 KB
steps/create.mdmarkdown11.3 KB
steps/revise.mdmarkdown7.5 KB
steps/validate.mdmarkdown6.1 KB

steps/create.md

View on GitHub
# Step: create

Synthesise a new TRACK.md (and optionally ALBUM.md) from a music brief. Default verb when no other verb matches.

## Inputs

- `<brief>` — the music description. Free text. Examples: "indie folk track about a long winter", "make me a melodic-trap EP about leaving home, 4 tracks, 2010s lo-fi feel".
- `-f <path/to/ARTIST.md>` — optional. Bind the artifact to an artist identity. Reads voice profile, custom model, recurring instrumentation, rights posture from the bound ARTIST.md.

## Workflow

### 1. Detect album mode

Scan the brief for multi-track signals:

- Words: "EP", "album", "record", "mixtape", "side A / side B", explicit track counts ("4-track", "5 songs"), or numbered track lists in the brief.
- Plural "tracks" or "songs" with no qualifier → ambiguous; ask.

An explicit album, EP, numbered track list or track count selects album mode: produce `ALBUM.md` and per-track folders under `tracks/` without renewed confirmation. Ask through available question tooling or plain text only when plural intent or the requested scope remains ambiguous. Otherwise proceed in single-track mode.

### 2. Read ARTIST.md if bound

When `-f` was passed, read the file. Extract:

- `voice_profile` (if any) — sets `voice_profile` in TRACK.md frontmatter; drops vocal descriptors from Style; biases Audio Influence to 78%.
- `custom_model` (if any) — sets `custom_model` in frontmatter; drops redundant genre/era from Style.
- `recurring_instruments` — biases the Style of Music descriptor stack toward these.
- `rights_posture` — surfaces in the user-facing summary; not repeated in TRACK.md.

If `-f` is missing, treat as no artist binding. Skip these defaults.

### 3. Auto-detect sufficient specification

Use these dimensions to identify information that would materially change the requested result:

| Dimension | Detection signal |
|-----------|------------------|
| Genre | Named genre / subgenre, or near-synonym |
| Mood | Mood adjectives (nostalgic, brooding, euphoric, glacial, etc.) |
| Vocal direction | Gender / register / delivery / "no vocals" / "instrumental" |
| Length target | Time-format like "3:30", or "single", "long-form", "sketch" |
| References | Era ("late-90s", "2010s"), regional scene ("Bristol post-punk"), or sound-fingerprint description |

Reuse ARTIST.md defaults when bound. State routine musical assumptions and proceed; batch only consequential unresolved questions. Do not infer rights or voice consent from a musical assumption, and do not ask merely because fewer than three dimensions are stated.

### 4. Synthesise the prompt block

Field-by-field. The composing rules live in [`../references/style-and-lyrics.md`](../references/style-and-lyrics.md) (descriptor stack, bracket metatag canon, lyric flow, languages, phonetic/delivery control, SFX warning, consolidated pitfalls). Slider settings and Voice / Custom Model adjustments live in [`../references/sliders-and-personalization.md`](../references/sliders-and-personalization.md). For copy-paste-ready genre recipes, see [`../references/genre-templates.md`](../references/genre-templates.md):

**Style of Music** — 4 to 7 descriptors, ordered: genre → era → mood → instruments → vocal direction. Comma-separated. Front-load the genre. Add BPM as the last item when known. Total ≤ 1000 chars; aim 280–730. When a Voice is attached, omit the vocal-direction descriptor entirely.

**Lyrics** — bracketed structural metatags ([Intro], [Verse 1], [Pre-Chorus], [Chorus], [Bridge], [Outro]) on their own lines. Stack 1–3 inline cues per section: instrumentation, texture, vocal delivery. Use parenthetical cues sparingly for performance direction (`(whispered)`, `(belted)`, `(building intensity)`). Phonetic spelling for unusual proper nouns. Total ≤ 5000 chars. Skip the Lyrics section entirely for instrumental tracks; mark the brief `[Instrumental]` and toggle Suno's Instrumental setting in the user-facing summary. When the user wants help writing or shaping the lyrics — not when they supply finished lines — consult [`../references/songwriting-craft.md`](../references/songwriting-craft.md) for structure, rhyme, meter, hook, and prosody; it aids singable lyrics and never restyles lines the user already wrote.

**Exclude Styles** — 0 to 3 tags. Use sparingly: positives define, negatives refine. Common candidates: `male vocals`, `female vocals`, `autotune`, `heavy distortion`, `pop hooks`, `808s`, `EDM drops`, `drums`, `piano`. Cap at 3 — more produces mush.

**Sliders** — per-genre defaults from [`../references/sliders-and-personalization.md`](../references/sliders-and-personalization.md) § *Slider bands by genre*, adjusted for Voice / Custom Model:

| Genre family | Weirdness | Style Influence | Audio Influence (only if Voice/Model) |
|--------------|-----------|-----------------|---------------------------------------|
| Radio pop | 35–50 | 65–80 | 60–75 |
| Hip-hop / trap | 40–55 | 55–70 | 60–80 |
| Worship / gospel | 25–40 | 70–85 | 70–90 |
| Cinematic orchestral | 55–70 | 45–60 | n/a |
| Ambient / experimental | 70–85 | 35–55 | n/a |
| Indie folk / pop | 30–45 | 70–85 | 70–85 |

Pick the band that best matches the brief; centre within the band; explain in the Rationale.

### 5. Assemble TRACK.md

Use the schema from [`../references/track-schema.md`](../references/track-schema.md). Order strictly: frontmatter → Title → Suno prompt block (Style fenced, Lyrics fenced, Exclude fenced) → Sliders → Voice / Custom Model → Rationale → Iteration log.

The first iteration log entry on `create`:

```
- v0 (YYYY-MM-DD): initial draft from brief — "<one-line brief paraphrase>"
```

The `revise` step appends entries with the same shape.

### 6. Assemble ALBUM.md if album mode

When step 1 selects album mode, produce `ALBUM.md` alongside the per-track files. Schema in `references/track-schema.md` § ALBUM. Sections: concept, arc (opening / development / climax / closing), tracklist (numbered, each line: `nn. Title — BPM — key — feel`), transitions (key changes, BPM ramps, cross-fades), rights-and-distribution placeholder.

For an N-track album, scaffold the `tracks/01-{slug}/`, `tracks/02-{slug}/`, … directories. Synthesise each TRACK.md in the same pass — the album arc informs each track's Rationale section, and the tracklist transitions get cross-referenced from each TRACK.md's iteration log.

### 7. Validate, then write

Allocate a unique temp folder for this invocation so parallel projects cannot
overwrite each other's drafts:

```bash
python3 -c 'import tempfile; print(tempfile.mkdtemp(prefix="suno-draft-"))'
```

Keep the printed absolute path as `$DRAFT_DIR` (substitute that literal path when
shell state does not persist). Write drafts there with canonical filenames because
[`../scripts/validate.py`](../scripts/validate.py) dispatches on them. In album
mode, mirror the project layout under `$DRAFT_DIR` so one directory walk covers
ALBUM.md and every TRACK.md. Validate that directory for an album; for a single
track use:

`$SKILL_DIR` = this skill's folder — `${CLAUDE_SKILL_DIR}` in Claude Code, the directory containing the skill's SKILL.md elsewhere.

```bash
python3 "$SKILL_DIR"/scripts/validate.py "$DRAFT_DIR/TRACK.md"
```

- **GREEN** (exit 0) → `mv` the draft into place, no surfacing in summary.
- **YELLOW** (exit 2) → `mv` the draft into place, warnings included in user-facing summary verbatim.
- **RED** (exit 1) → block the move. Fix the issue in the temp draft (re-tighten descriptor count, trim Lyrics, drop SFX brackets) and re-validate — the final path is never touched by RED content. Do not ask the user — the model fixes and retries up to twice. If still RED on the third attempt, surface the validator output and stop.

Move only the validated drafts from this invocation's `$DRAFT_DIR`; remove its
empty staging folders after success and keep drafts on failure. Create a given
target project one invocation at a time.

### 8. Emit `.gitignore` if missing

When the project folder has no `.gitignore`, write one with:

```gitignore
audio/
*.wav
*.mp3
*.flac
*.m4a
.DS_Store
```

Audio takes are large and not worth versioning. Prompts are durable; audio is not. The user can override locally if they want to commit a specific take.

### 9. Print the user-facing summary

Output in conversation:

- Path to the TRACK.md (and ALBUM.md if applicable)
- A single-line copy-paste pointer: `Open {path}/TRACK.md, copy the Style / Lyrics / Exclude blocks into Suno's Custom Mode.`
- Slider settings the user needs to set in the Suno UI explicitly (the sliders are not auto-applied — they are emitted as instructions)
- Any YELLOW validator warnings, verbatim
- If ARTIST.md was bound: which artist defaults flowed in, which were overridden by the brief
- Rights reminder if ARTIST.md is set up: short pointer to `references/rights-and-deprecation.md` summary
- **My Taste reminder** when this is the first track for a new artist or an evaluation/A-B run: `Suno's My Taste personalization is default-on. Disable from avatar menu > My Taste during evaluation work — otherwise the variable is uncontrolled.` See [`../references/sliders-and-personalization.md`](../references/sliders-and-personalization.md) § *My Taste*.

### 10. Iteration handoff

End with: `When you've listened, run /suno-produce revise {path} "<feedback>"` — primes the next loop.

## Edge cases

- **Brief names an artist or a copyrighted entity** ("a Sufjan Stevens track", "voice like Adele", "in the style of Daft Punk") — translate to sound-fingerprint descriptors before synthesis. Hard rule, both legal (rights exposure on a discoverable prompt) and functional (Suno filters or ignores the citation, model collapses to averaged tag). The validator will RED any citation pattern that survives. Worked rewrites: "Sufjan Stevens" → "indie folk, intimate fingerpicked acoustic, soft male tenor, banjo, breathy delivery, lo-fi tape warmth"; "Adele-like voice" → "full-throated contralto female, gospel-rasp belt, plate reverb, dry close-mic verse"; "Daft Punk vibe" → "French house, sidechain pump, vocoded vocal, filter sweeps, 4/4 at 120 BPM". Note the translation in Rationale so the user sees what was rewritten and why.
- **Brief is in a non-English language target** (e.g., "make me a French chanson") — write Lyrics in the target language directly. Avoid `[Bilingual]` and similar tags — they don't work alone. See [`../references/style-and-lyrics.md`](../references/style-and-lyrics.md) § *Languages and code-switching*.
- **Brief asks for SFX in lyrics** ("with applause", "with vinyl crackle") — Style-field texture instead, never Lyrics-field bracket. SFX brackets are unreliable. Note in Rationale that the user can layer specific SFX in Suno Studio after generation.
- **Brief asks for bar counts** ("8-bar verse") — bar-count tags don't work in Lyrics; honour rate < 30%. Surface that bar-count work belongs in Suno Studio's section editor, not in this prompt.
- **Brief changes ARTIST.md defaults** — apply an explicit musical override and report it. Ask only when the intended identity/profile remains ambiguous; do not infer voice consent or rights from a musical preference. Preserve the bound source file unless its update is requested.
- **Existing TRACK.md at the target path** — refuse to overwrite. Suggest `revise` instead. The `create` verb writes only to fresh paths.
- **Project folder collision** — if `{slug}/` exists with non-skill content, refuse. Ask for an explicit slug.
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall