Source profileQuality 90/100

bitwize-music-studio/claude-ai-music-skills/skills/pre-generation-check/SKILL.md

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".

Source repository stars
446
Declared platforms
0
Static risk flags
0
Last source update
2026-08-23
Source checked
2026-08-25

Decision brief

What it does: where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill "skills/pre-generation-check"
    Safe inspection promptEditorial

    Inspect the Agent Skill "pre-generation-check" from https://github.com/bitwize-music-studio/claude-ai-music-skills/blob/b1b11a67e8ce5dd07691b68cf736cff8e4c55c87/skills/pre-generation-check/SKILL.md at commit b1b11a67e8ce5dd07691b68cf736cff8e4c55c87. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Workflow

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

      Call runpregenerationgates(albumslug, trackslug) — returns all 6 gate resultsFormat pass/fail report from MCP responseOutput verdict: READY or NOT READY
    2. 02

      Your Task

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

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

      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.

      Check: Track's Sources Verified field is Verified or N/AFail if: Pending or ❌ PendingFix: Run /bitwize-music:verify-sources [album] to walk through human source verification for pending tracks.
    4. 04

      Instrumental Track Detection

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

      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:Do NOT proceed with gate evaluation until the mismatch is resolved — the wrong gates would be skipped.
    5. 05

      The 6 Gates

      Check: Track's Sources Verified field is Verified or N/A

      Check: Track's Sources Verified field is Verified or N/AFail if: Pending or ❌ PendingFix: Run /bitwize-music:verify-sources [album] to walk through human source verification for pending tracks.

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score90/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars446SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    bitwize-music-studio/claude-ai-music-skills
    Skill path
    skills/pre-generation-check/SKILL.md
    Commit
    b1b11a67e8ce5dd07691b68cf736cff8e4c55c87
    License
    CC0-1.0
    Collected
    2026-08-25
    Default branch
    main
    View the original SKILL.md

    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.

    Frequently asked questions

    What to verify before installation and use

    What does the pre-generation-check source document cover?

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

    How do I install pre-generation-check?

    The source record exposes this install command: npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill "skills/pre-generation-check". Inspect the command and pinned source before running it.

    Alternatives

    Compare before choosing

    Computed 10045,511

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    Computed 10045,511

    coreyhaines31/marketingskills

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

    Computed 10024,921

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    Computed 10015,122

    wanshuiyin/Auto-claude-code-research-in-sleep

    citation-audit

    Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.