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".
What this skill does
## 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
- **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
```markdown
# 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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.