/validate-album
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
$ npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill validate-album --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/validate-album
Context preview
The summary Claude sees to decide when to auto-load this skill.
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
SKILL.md
validate-album.SKILL.mdname: validate-album
description: Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
argument-hint: <album-name>
model: haiku
context: fork
allowed-tools:
- Read
- Bash
- Glob
- Grep
- bitwize-music-mcp
Album Validator Agent
Your Task
**Input**: $ARGUMENTS (album name, e.g., `sample-album`)
Validate that an album has all required files in the correct locations, catching path issues and missing content before they become problems.
---
Step 1: Load Config & Find Album
1. Call `get_config()` — returns paths (`content_root`, `audio_root`, `documents_root`) and `artist.name`
- If config missing, STOP and report:
[FAIL] Config file missing: ~/.bitwize-music/config.yaml
Run /configure to set up the plugin.2. Call `find_album(album_name)` — fuzzy match by name, slug, or partial
- If not found, STOP and report (MCP returns available albums):
[FAIL] Album not found: {album-name}3. Optionally call `validate_album_structure(album_slug)` — runs structural validation checks and returns `{passed, failed, warnings, skipped, issues[], checks[]}`. This MCP tool handles directory structure, required files, audio placement, and track content checks in one call.
**Note**: The MCP `validate_album_structure` tool performs many of the checks below automatically. You can use its results directly or run the manual checks for more detailed reporting.
---
Step 3: Run Validations
Initialize Counters
- `passed = 0`
- `failed = 0`
- `warnings = 0`
- `skipped = 0`
- `issues = []` (list of fix commands)
Output Header
═══════════════════════════════════════════════════════════
ALBUM VALIDATION: {album-name}
═══════════════════════════════════════════════════════════---
Validation Categories
CONFIG
CONFIG
──────
| Check | Pass | Fail | |-------|------|------| | Config file exists | `[PASS] Config file exists` | `[FAIL] Config file missing` | | content_root defined | `[PASS] content_root: {value}` | `[FAIL] content_root not defined` | | audio_root defined | `[PASS] audio_root: {value}` | `[FAIL] audio_root not defined` | | artist defined | `[PASS] artist: {value}` | `[FAIL] artist.name not defined` |
ALBUM STRUCTURE
ALBUM STRUCTURE
───────────────
| Check | How | Pass | Fail | |-------|-----|------|------| | Album dir exists | `test -d {album_path}` | `[PASS] Album directory: {path}` | `[FAIL] Album directory missing` | | README.md exists | `test -f {album_path}/README.md` | `[PASS] README.md exists` | `[FAIL] README.md missing` | | tracks/ dir exists | `test -d {album_path}/tracks` | `[PASS] tracks/ directory exists` | `[FAIL] tracks/ directory missing` | | Track files exist | `ls {album_path}/tracks/*.md` | `[PASS] {N} track files found` | `[WARN] No track files found` |
**For documentary albums** (check README.md for type): | Check | How | Pass | Fail | |-------|-----|------|------| | RESEARCH.md exists | `test -f {album_path}/RESEARCH.md` | `[PASS] RESEARCH.md exists` | `[WARN] RESEARCH.md missing (documentary album)` | | SOURCES.md exists | `test -f {album_path}/SOURCES.md` | `[PASS] SOURCES.md exists` | `[WARN] SOURCES.md missing (documentary album)` |
AUDIO FILES
AUDIO FILES
───────────
Expected path: `{audio_root}/artists/{artist}/albums/{genre}/{album}/`
| Check | How | Pass | Fail | |-------|-----|------|------| | Audio dir exists (correct path) | `test -d {audio_root}/artists/{artist}/albums/{genre}/{album}` | `[PASS] Audio directory: {path}` | See below | | Audio dir in wrong location | `test -d {audio_root}/{album}` | N/A | `[FAIL] Audio in wrong location (missing artist folder)` |
**If audio in wrong location**, add to issues:
→ Expected: {audio_root}/artists/{artist}/albums/{genre}/{album}/
→ Found at: {audio_root}/{album}/ (WRONG - missing artist folder)
→ Fix: mv {audio_root}/{album}/ {audio_root}/artists/{artist}/albums/{genre}/{album}/| Check | How | Pass | Skip | |-------|-----|------|------| | WAV files present | `ls {audio_path}/*.wav` | `[PASS] {N} WAV files found` | `[SKIP] No audio files yet` | | mastered/ exists | `test -d {audio_path}/mastered` | `[PASS] mastered/ directory exists` | `[SKIP] Not mastered yet` |
ALBUM ART
ALBUM ART
─────────
| Check | How | Pass | Skip | |-------|-----|------|------| | Art in audio folder | `test -f {audio_path}/album.png` | `[PASS] album.png in audio folder` | `[SKIP] No album art yet` | | Art in content folder | `test -f {album_path}/album-art.*` | `[PASS] album-art in content folder` | `[SKIP] No album art yet` |
TRACKS
TRACKS
──────
For each track file in `{album_path}/tracks/*.md`:
1. Read the file 2. Check for required fields:
- Status field exists
- Suno Style Box exists (has `## Suno Inputs` section)
- Suno Lyrics Box exists
- If Status is `Generated` or `Final`: Suno Link present
- If documentary: Sources Verified status
3. Check instrumental field sync:
- Read frontmatter `instrumental` field (true/false/missing)
- Read Track Details table `**Instrumental**` row (Yes/No/missing)
- If both present and they disagree → `[WARN] {filename} - Instrumental field mismatch: frontmatter={value}, table={value}`
- If only one is set → `[WARN] {filename} - Instrumental field missing from {frontmatter|table} (set in {other})`
Output per track:
- `[PASS] {filename} - Status: {status}, Suno Link: {present/missing}`
- `[WARN] {filename} - Status: {status}, missing {what}`
- `[FAIL] {filename} - No Status field`
---
Step 4: Summary
═══════════════════════════════════════════════════════════
SUMMARY: {passed} passed, {failed} failed, {warnings} warning(s), {skipped} skipped
═══════════════════════════════════════════════════════════If any issues:
ISSUES TO FIX:
1. {issue description}
{fix command}
2. ...Read more
name: validate-album description: Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health. argument-hint: <album-name> model: haiku context: fork allowed-tools: - Read - Bash - Glob - Grep - bitwize-music-mcp
Album Validator Agent
Your Task
**Input**: $ARGUMENTS (album name, e.g., `sample-album`)
Validate that an album has all required files in the correct locations, catching path issues and missing content before they become problems.
---
Step 1: Load Config & Find Album
1. Call `get_config()` — returns paths (`content_root`, `audio_root`, `documents_root`) and `artist.name`
- If config missing, STOP and report:
[FAIL] Config file missing: ~/.bitwize-music/config.yaml
Run /configure to set up the plugin.2. Call `find_album(album_name)` — fuzzy match by name, slug, or partial
- If not found, STOP and report (MCP returns available albums):
[FAIL] Album not found: {album-name}3. Optionally call `validate_album_structure(album_slug)` — runs structural validation checks and returns `{passed, failed, warnings, skipped, issues[], checks[]}`. This MCP tool handles directory structure, required files, audio placement, and track content checks in one call.
**Note**: The MCP `validate_album_structure` tool performs many of the checks below automatically. You can use its results directly or run the manual checks for more detailed reporting.
---
Step 3: Run Validations
Initialize Counters
- `passed = 0`
- `failed = 0`
- `warnings = 0`
- `skipped = 0`
- `issues = []` (list of fix commands)
Output Header
═══════════════════════════════════════════════════════════
ALBUM VALIDATION: {album-name}
═══════════════════════════════════════════════════════════---
Validation Categories
CONFIG
CONFIG ──────
| Check | Pass | Fail | |-------|------|------| | Config file exists | `[PASS] Config file exists` | `[FAIL] Config file missing` | | content_root defined | `[PASS] content_root: {value}` | `[FAIL] content_root not defined` | | audio_root defined | `[PASS] audio_root: {value}` | `[FAIL] audio_root not defined` | | artist defined | `[PASS] artist: {value}` | `[FAIL] artist.name not defined` |
ALBUM STRUCTURE
ALBUM STRUCTURE ───────────────
| Check | How | Pass | Fail | |-------|-----|------|------| | Album dir exists | `test -d {album_path}` | `[PASS] Album directory: {path}` | `[FAIL] Album directory missing` | | README.md exists | `test -f {album_path}/README.md` | `[PASS] README.md exists` | `[FAIL] README.md missing` | | tracks/ dir exists | `test -d {album_path}/tracks` | `[PASS] tracks/ directory exists` | `[FAIL] tracks/ directory missing` | | Track files exist | `ls {album_path}/tracks/*.md` | `[PASS] {N} track files found` | `[WARN] No track files found` |
**For documentary albums** (check README.md for type): | Check | How | Pass | Fail | |-------|-----|------|------| | RESEARCH.md exists | `test -f {album_path}/RESEARCH.md` | `[PASS] RESEARCH.md exists` | `[WARN] RESEARCH.md missing (documentary album)` | | SOURCES.md exists | `test -f {album_path}/SOURCES.md` | `[PASS] SOURCES.md exists` | `[WARN] SOURCES.md missing (documentary album)` |
AUDIO FILES
AUDIO FILES ───────────
Expected path: `{audio_root}/artists/{artist}/albums/{genre}/{album}/`
| Check | How | Pass | Fail | |-------|-----|------|------| | Audio dir exists (correct path) | `test -d {audio_root}/artists/{artist}/albums/{genre}/{album}` | `[PASS] Audio directory: {path}` | See below | | Audio dir in wrong location | `test -d {audio_root}/{album}` | N/A | `[FAIL] Audio in wrong location (missing artist folder)` |
**If audio in wrong location**, add to issues:
→ Expected: {audio_root}/artists/{artist}/albums/{genre}/{album}/
→ Found at: {audio_root}/{album}/ (WRONG - missing artist folder)
→ Fix: mv {audio_root}/{album}/ {audio_root}/artists/{artist}/albums/{genre}/{album}/| Check | How | Pass | Skip | |-------|-----|------|------| | WAV files present | `ls {audio_path}/*.wav` | `[PASS] {N} WAV files found` | `[SKIP] No audio files yet` | | mastered/ exists | `test -d {audio_path}/mastered` | `[PASS] mastered/ directory exists` | `[SKIP] Not mastered yet` |
ALBUM ART
ALBUM ART ─────────
| Check | How | Pass | Skip | |-------|-----|------|------| | Art in audio folder | `test -f {audio_path}/album.png` | `[PASS] album.png in audio folder` | `[SKIP] No album art yet` | | Art in content folder | `test -f {album_path}/album-art.*` | `[PASS] album-art in content folder` | `[SKIP] No album art yet` |
TRACKS
TRACKS ──────
For each track file in `{album_path}/tracks/*.md`:
1. Read the file 2. Check for required fields:
- Status field exists
- Suno Style Box exists (has `## Suno Inputs` section)
- Suno Lyrics Box exists
- If Status is `Generated` or `Final`: Suno Link present
- If documentary: Sources Verified status
3. Check instrumental field sync:
- Read frontmatter `instrumental` field (true/false/missing)
- Read Track Details table `**Instrumental**` row (Yes/No/missing)
- If both present and they disagree → `[WARN] {filename} - Instrumental field mismatch: frontmatter={value}, table={value}`
- If only one is set → `[WARN] {filename} - Instrumental field missing from {frontmatter|table} (set in {other})`
Output per track:
- `[PASS] {filename} - Status: {status}, Suno Link: {present/missing}`
- `[WARN] {filename} - Status: {status}, missing {what}`
- `[FAIL] {filename} - No Status field`
---
Step 4: Summary
═══════════════════════════════════════════════════════════
SUMMARY: {passed} passed, {failed} failed, {warnings} warning(s), {skipped} skipped
═══════════════════════════════════════════════════════════If any issues:
ISSUES TO FIX:
1. {issue description}
{fix command}
2. ...Showing the first part of this file.
I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling.
Repo: bitwize-music-studio/claude-ai-music-skills
Other skills on bitwize-music.
- /about
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or capabilities.
Open skill - /album-art-director
Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual artwork generation.
Open skill - /album-conceptualizer
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.
Open skill - /album-dashboard
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.
Open skill - /album-ideas
Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.
Open skill - /clipboard
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard. Use when the user needs to paste lyrics or style prompts into Suno or other external tools.
Open skill

