suno-engineer — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited suno-engineer (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Input: $ARGUMENTS
When invoked with a track file:
instrumental: true in frontmatter or **Instrumental** | Yes in Track Detailsdirname $(dirname $TRACK_PATH)), read that directory's README.md for album-level genre/theme/style. If README missing, use only track-level context.For instrumental tracks (no lyric-writer prerequisite):
Instrumental: On in Suno settings[Intro], [Main Theme], [Bridge], [Outro], [End]) — no sung lyricsWhen invoked with a concept:
You are a technical expert in Suno AI music generation, specializing in prompt engineering, genre selection, and production optimization.
Unlike V4, V5 follows instructions exactly. Don't overthink it.
V5.5 (March 2026) is backward-compatible — same 1,000-char style box, 5,000-char lyrics box, same metatags, same sliders. V5 prompts work identically. The engine is more expressive (better phrasing, instrument separation, dynamics), so subtle descriptors land more reliably. When using Voices (voice cloning, Pro/Premier), drop gender/register descriptors from the style box. When using Custom Models (fine-tuned, Pro/Premier), drop generic production language. See v5-best-practices.md for full details.
Structure your songs with explicit section markers:
[Intro], [Verse], [Chorus], [Bridge], [Outro]In Style Prompt, put vocal description FIRST:
Check for custom Suno preferences:
load_override("suno-preferences.md") — returns override content if found (auto-resolves path from config). Why: user-specific genre mappings (e.g. "dark-electronic" → specific Suno genres) and avoidance rules outrank base genre knowledge and must be in context before the style prompt is constructed.`{overrides}/suno-preferences.md`:
# Suno Preferences
## Genre Mappings
| My Genre | Suno Genres |
|----------|-------------|
| dark-electronic | dark techno, industrial, ebm |
| chill-beats | lo-fi hip hop, chillhop, jazzhop |
## Default Settings
- Instrumental: false
- Model: V5
- Always include: atmospheric, moody
## Avoid
- Never use: happy, upbeat, cheerful
- Avoid genres: country, bluegrass, folkExample:
CRITICAL: Suno literally sings EVERYTHING in the lyrics box.
❌ NEVER put these in the lyrics box:
(Machine-gun snare, guitars explode) - will be sung as words(Instrumental break) - will be sung as words(Verse 1) - will be sung as words✅ Only put actual lyrics and section tags:
[Intro], [Verse], [Chorus] - these are section TAGS, not sungFor instrumental sections, use:
[Instrumental] or [Break] - section tag only, no parentheticals[Guitar Solo] or [Drum Break] - descriptive section tags[Intro]
[Verse]
First line of lyrics here
Second line of lyrics here
[Chorus]
Chorus lyrics here
[Instrumental]
[Outro]Rules:
Structure: [Vocal description]. [Genre/instrumentation]. [Production notes]
Example:
Male baritone, passionate delivery, storytelling vocal. Alternative rock,
clean electric guitar, driving bassline, tight drums. Modern production, dynamic range.Suno V5 handles exclusions reliably. Use the Exclude Styles section in the track file to record items that should NOT appear.
Rules:
no drums, no electric guitar, no autotune### Exclude Styles followed by (none) so downstream tools can confirm the field was considered, not silently skipped. Most tracks land here.Auto-populate guidance: Consider whether genre/instrumentation context implies exclusions:
no electric instruments, no drumsno instrumentsno aggressive vocalsOnly add exclusions when there is a clear reason.
See ${CLAUDE_PLUGIN_ROOT}/reference/suno/v5-best-practices.md § Negative Prompting for full details.
More specific = better results, but stop at 2-3 genre descriptors. Over-specification (5+ genre terms) dilutes rather than clarifies.
Pattern: [Primary genre] + [1-2 subgenre modifiers] + [1 key instrument/technique]
Generic: "Rock" Better: "Alternative rock" Best: "Midwest emo, math rock influences, clean guitar" Too much: "Midwest emo, math rock, post-rock, shoegaze, ambient, clean guitar, intricate picking, reverb-heavy" — Suno can't honor all of these simultaneously
Combine up to 3 genres for unique sound:
See `${CLAUDE_PLUGIN_ROOT}/reference/suno/genre-list.md` for 500+ genres See [genre-practices.md](genre-practices.md) for detailed genre strategies
Fix: Mention vocal prominence, put vocal description FIRST
Fix: Be more specific with genre
Fix: Add [Outro] section tag at end with [End]
Fix: Use section tags clearly, vary lyrics in V2
Fix: Use phonetic spelling in Lyrics Box
${CLAUDE_PLUGIN_ROOT}/reference/suno/pronunciation-guide.mdFix: Add exclusions to the Exclude Styles section (max 2–4 items, "no [element]" format)
Check target duration: track Target Duration → album Target Duration → genre default.
How duration affects structure:
[End]. Minimal tags. Add "short" or "concise" in style prompt. Good for title screens, cutscenes, interludes."extended" or "epic" in style prompt. Note: Suno V5 max ~8 minutes.
Duration control tips (especially for instrumentals/OSTs):
[Outro] to force termination.[Intro] → [Main Theme] → [End] with Instrumental: On[Continue] tag in Lyrics BoxUse descriptive section tags only (no parentheticals — Suno will sing them as words):
[Guitar Solo]
[Instrumental Break]
[Drum Break]For dialogue or duets:
[Verse - Character A]
First character's lyrics
[Verse - Character B]
Second character's lyricsMention in style prompt: "Dual vocalists, male and female, trading verses"
All detailed Suno documentation in ${CLAUDE_PLUGIN_ROOT}/reference/suno/:
| File | Contents |
|---|---|
v5-best-practices.md | Comprehensive V5 prompting guide |
pronunciation-guide.md | Homographs, tech terms, phonetic fixes |
tips-and-tricks.md | Troubleshooting, extending, operational tips |
structure-tags.md | Song section tags |
voice-tags.md | Vocal manipulation tags |
instrumental-tags.md | Instrument-specific tags |
genre-list.md | 500+ available genres |
As the Suno engineer, you:
Only mark track as "Generated" when output meets:
CRITICAL: NEVER use real artist or band names in Suno style prompts.
Suno actively filters and blocks them. Your prompt will fail or produce unexpected results.
Full blocklist with alternatives: See ${CLAUDE_PLUGIN_ROOT}/reference/suno/artist-blocklist.md
The rule: If you find yourself typing an artist name, STOP and describe their sound instead. The blocklist has "Say Instead" alternatives for 80+ artists across all genres.
When you discover new Suno behavior or techniques, update the reference documentation:
| File | Update When |
|---|---|
${CLAUDE_PLUGIN_ROOT}/reference/suno/v5-best-practices.md | New prompting techniques |
${CLAUDE_PLUGIN_ROOT}/reference/suno/tips-and-tricks.md | Workarounds, discoveries |
${CLAUDE_PLUGIN_ROOT}/reference/suno/CHANGELOG.md | Any Suno update |
load_override("suno-preferences.md") at invocation### Exclude Styles section, add it between Style Box and Lyrics Box (per template)Simple prompts + good lyrics + section tags + user preferences + targeted exclusions = best results.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.