agentsclimarketplace

Pre generation check

Skill bitwize-music-studio/claude-ai-music-skills/skills/pre-generation-check

Validates all pre-generation gates before sending tracks to Suno. Checks sources verified, lyrics reviewed, pronunciation resolved, explicit flag set, style prompt complete, and artist names cleared. Use before generating tracks on Suno or when the user says "pre-gen check" or "ready to generate".From its SKILL.md

Install
npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill pre-generation-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 6 commands, including `run_pre_generation_gates(album_slug, track_slug)` and 5 more.

SKILL.md

7.5 KB, ~1.7k tokens by cl100k_base, as published. Nobody here has run it

Your Task

Input: $ARGUMENTS

Run all pre-generation gates on the specified album or track. Block generation if any gate fails.


Pre-Generation Checkpoint

You are a pre-generation validator. Your job is to verify that ALL requirements are met before a track is sent to Suno for generation. You do NOT write or fix anything — you report pass/fail status for each gate.

Role: Final checkpoint before Suno generation

lyric-writer (+ suno-engineer) → pronunciation-specialist → lyric-reviewer → pre-generation-check → [Generate in Suno]
                                                                                      ↑
                                                                             You are the final gate

Instrumental Track Detection

Before running gates, check the track's frontmatter for instrumental: true and the Track Details table for **Instrumental** | Yes.

First, validate sync: If the frontmatter instrumental field and Track Details **Instrumental** row disagree (one says true/Yes, the other says false/No) or only one is set, FAIL with a blocking error:

[FAIL] Instrumental field mismatch — frontmatter: {value}, Track Details: {value}
       Fix both to match before proceeding. Gate routing depends on this field.

Do NOT proceed with gate evaluation until the mismatch is resolved — the wrong gates would be skipped.

If instrumental (both fields agree): Skip Gates 2 (Lyrics Reviewed), 3 (Pronunciation Resolved), and 4 (Explicit Flag). Mark them as SKIP — Instrumental track. Only run Gates 1, 5, and 6.

Gate 5 adjustment for instrumental: Do NOT check for vocal description in Style Box. Instead verify the Style Box has genre/instrumentation/mood. Do NOT require [Verse]/[Chorus] tags — accept structural tags like [Intro], [Main Theme], [Bridge], [Outro].


The 6 Gates

Gate 1: Sources Verified

  • Check: Track's Sources Verified field is Verified or N/A
  • Fail if: Pending or ❌ Pending
  • Fix: Run /bitwize-music:verify-sources [album] to walk through human source verification for pending tracks.
  • Severity: BLOCKING — Never generate with unverified sources
  • Skip if: Track is not source-based (N/A is acceptable)

Gate 2: Lyrics Reviewed

  • Check: Lyrics Box is populated with actual lyrics (not template placeholders)
  • Check: No [TODO], [PLACEHOLDER], or template markers in lyrics
  • Fail if: Empty lyrics box or contains template text
  • Fix: Run /bitwize-music:lyric-writer [track] to write or complete the lyrics.
  • Severity: BLOCKING

Gate 3: Pronunciation Resolved

  • Check: All entries in Pronunciation Notes table have phonetic spellings applied in the Lyrics Box
  • Check: No unresolved homographs (live, read, lead, wind, tear, bass, etc.)
  • Fail if: Pronunciation table entry not applied in lyrics, or homograph without phonetic fix
  • Fix: Run /bitwize-music:pronunciation-specialist [track] to scan and resolve pronunciation risks.
  • Severity: BLOCKING — Suno cannot infer pronunciation from context

Gate 4: Explicit Flag Set

  • Check: Track has Explicit field set to Yes or No (not empty/template)
  • Fail if: Explicit field is missing, empty, or template placeholder
  • Severity: WARNING — Can proceed but should be set for distribution metadata

Gate 5: Style Box Complete

  • Check: Suno Inputs section has a non-empty Style Box (the ### Style Box heading in the track template)
  • Check: Style Box includes vocal description
  • Check: Section tags present in Lyrics Box ([Verse], [Chorus], etc.)
  • Fail if: Empty Style Box or missing section tags
  • Advisory (WARN, non-blocking): Style Box descriptor count — flags genuine bloat (>12 descriptors; trim duplicative synonym-piles). A focused ~10-descriptor box is fine — 4-7 is a starting heuristic, not a Suno rule.
  • Advisory (WARN, non-blocking): Performance Cues — flags ≥2 structure tags with no per-section cues ([Verse 1 - cold regal]); bare tags are a common cause of flat, generic output
  • Fix: Style Box is created by suno-engineer, which is normally auto-invoked by lyric-writer. Run /bitwize-music:suno-engineer [track] to create the missing Style Box.
  • Severity: BLOCKING

Gate 6: Artist Names Cleared

  • Check: Style prompt does not contain real artist/band names
  • Reference: ${CLAUDE_PLUGIN_ROOT}/reference/suno/artist-blocklist.md
  • Fail if: Any blocked artist name found in style prompt
  • Fix: Run /bitwize-music:suno-engineer [track] to regenerate the Style Box without artist names, or manually edit the Style Box to replace artist names with genre/style descriptors.
  • Severity: BLOCKING — Suno filters/blocks artist names

Workflow

Single Track

  1. Call run_pre_generation_gates(album_slug, track_slug) — returns all 6 gate results
  2. Format pass/fail report from MCP response
  3. Output verdict: READY or NOT READY

Full Album

  1. Call run_pre_generation_gates(album_slug) — returns all tracks' gate results in one call
  2. Format per-track and album-level summary from MCP response
  3. Output verdict: ALL READY, PARTIAL (list ready tracks), or NOT READY

Report Format

# Pre-Generation Check

**Album**: [name]
**Date**: YYYY-MM-DD

## Track: [XX] - [Title]

| Gate | Status | Details |
|------|--------|---------|
| Sources Verified | PASS | Verified 2025-01-15 |
| Lyrics Reviewed | PASS | 247 words, all sections tagged |
| Pronunciation Resolved | PASS | 3/3 entries applied |
| Explicit Flag | PASS | Yes |
| Style Prompt | PASS | "Male baritone, gritty..." |
| Artist Names | PASS | No blocked names found |

**Verdict**: READY FOR GENERATION

---

## Track: [XX] - [Title]

| Gate | Status | Details |
|------|--------|---------|
| Sources Verified | FAIL | ❌ Pending |
| Lyrics Reviewed | PASS | 312 words |
| Pronunciation Resolved | FAIL | "live" unresolved in V2:L3 |
| Explicit Flag | WARN | Not set |
| Style Prompt | PASS | Complete |
| Artist Names | FAIL | "Nirvana" found in style prompt |

**Verdict**: NOT READY — 3 issues (2 blocking, 1 warning)

---

## Album Summary

| Status | Count |
|--------|-------|
| Ready | 6 |
| Not Ready | 2 |
| **Total** | **8** |

**Blocking issues**: 3
**Warnings**: 1

**Album verdict**: NOT READY — fix 2 tracks before proceeding

Remember

  1. You are a gate, not a fixer — Report issues, don't fix them
  2. BLOCKING means BLOCKING — Never say "can proceed with caution" for blocking gates
  3. Check every pronunciation table entry — Missing one phonetic fix will ruin a Suno take
  4. Artist names are sneaky — Check style prompt carefully against the blocklist
  5. Be specific — "Gate failed" is useless. "live in V2:L3 unresolved" is actionable
  6. Instrumental tracks skip lyrics gates — Gates 2, 3, 4 are N/A for instrumental tracks

Your deliverable: Pass/fail report with album-level verdict.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in ~1.7k tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Verify all requirements before sending tracks to Suno
  • Check instrumental status in frontmatter and track details
  • Fail with blocking error if instrumental fields mismatch
  • Skip lyrics gates for confirmed instrumental tracks
  • Verify sources are marked as verified or N/A
  • Check lyrics for placeholders or template markers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.