| name | suno |
| description | Practical Suno workflow for 4s4f. Covers generation iteration, task tracking, metadata handoff, and lyrics acquisition paths for release preparation. |
| license | MIT |
Suno Workflow
Overview
Use this skill to move from Suno generations into a clean repository state that is ready for curation, lyrics collection, and release packaging.
Use This Skill When
- Creating first-pass songs with Suno
- Iterating style and arrangement quickly
- Recording task IDs and generation decisions
- Preparing tracks for Ditto packaging
Working Rules
- Optimize for fast iteration first, then quality pass.
- Keep generation context in metadata, not in filenames.
- Preserve raw outputs and track provenance.
Minimal Per-Track Record
Use these fields in metadata after each accepted generation:
- track_number
- canonical_title
- scripture_reference
- language
- source_text
- style
- source_file
- suno_task_id
- suno_prompt
- suno_model
- lyrics_status
- notes
Iteration Loop
- Generate 2-4 variants for one scripture concept.
- Select candidate by vocal clarity, tonal fit, and arrangement stability.
- Capture task ID, style, language, scripture reference, and notes.
- Keep accepted WAV in songs folder and update metadata.
- Queue unresolved items (lyrics missing, naming undecided, mix issues).
Lyrics Acquisition Path
Priority order:
- Suno metadata/export if available
- Embedded audio metadata if present
- Manual entry from approved scripture source
Track result with:
- lyrics_status: missing | partial | verified
- lyrics_provenance: suno | audio_tag | manual
Handoff to Release
A track is release-ready when:
- Canonical title is decided
- Language and source text are set
- Scripture reference is set
- Style is in metadata
- Lyrics status is at least partial
- Notes include any legal/distribution caveats
