跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

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

文档与办公539skills/pre-generation-check/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/bitwize-music-studio/claude-ai-music-skills/pre-generation-check/install.md ,按里面的步骤帮我安装这个 Skill。

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 Gates

The MCP tool behind this skill reports 8 blocking gates plus 3 advisories (Style Box Descriptor Count, Performance Cues, Generation Settings).

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: BLOCKING — the MCP gate fails closed when the flag is unset (#370)

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
  • Advisory (WARN, non-blocking): Generation Settings — the track's ### Generation Settings table must record a catalog model (v6, v6-wild, v6-mini, Custom: <name>) and Variety Off; at any higher Variety Suno rewrites the Style Box, so the descriptor checks above are meaningless. A PASS detail also notes when Max Mode is Off on a track targeting 2:30 or longer (Suno recommends it over two minutes; 2× credits). SKIP when the section is missing — add it from templates/track.md.
  • 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 gate results (8 blocking + 3 advisory)
  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 gate results (8 blocking + 3 advisory)
  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 |
| Generation Settings | PASS | Model v6, Variety Off, Max Mode On |

**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 | FAIL | Not set |
| Style Prompt | PASS | Complete |
| Artist Names | FAIL | "Nirvana" found in style prompt |
| Generation Settings | WARN | Variety is 'Normal' — set Off |

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

---

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

相似的 Skill

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

文档与办公

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

文档与办公

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

文档与办公

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

文档与办公

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

文档与办公

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

文档与办公