Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
bitwize-music-studio avatar

Validate Album

  • 148 installs
  • 400 repo stars
  • Updated July 31, 2026
  • bitwize-music-studio/claude-ai-music-skills

Review an album plan or draft release package for completeness, coherence, track order, metadata readiness, and pre-ship gaps before committing to distribution.

About

Validation skill that audits album readiness across tracklist, sequencing, metadata, and release-package completeness. It helps music projects catch structural gaps before mastering, marketing, or distribution workflows begin.

  • Tracklist completeness checks
  • Sequencing and coherence review
  • Metadata readiness audit
  • Pre-release gap detection
  • Release-package scoping

Validate Album by the numbers

  • 148 all-time installs (skills.sh)
  • Ranked #90 of 248 Release Management skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill validate-album

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs148
repo stars400
Last updatedJuly 31, 2026
Repositorybitwize-music-studio/claude-ai-music-skills

What it does

Review an album plan or draft release package for completeness, coherence, track order, metadata readiness, and pre-ship gaps before committing to distribution.

Files

SKILL.mdMarkdownGitHub ↗

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
──────
CheckPassFail
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
───────────────
CheckHowPassFail
Album dir existstest -d {album_path}[PASS] Album directory: {path}[FAIL] Album directory missing
README.md existstest -f {album_path}/README.md[PASS] README.md exists[FAIL] README.md missing
tracks/ dir existstest -d {album_path}/tracks[PASS] tracks/ directory exists[FAIL] tracks/ directory missing
Track files existls {album_path}/tracks/*.md[PASS] {N} track files found[WARN] No track files found

For documentary albums (check README.md for type):

CheckHowPassFail
RESEARCH.md existstest -f {album_path}/RESEARCH.md[PASS] RESEARCH.md exists[WARN] RESEARCH.md missing (documentary album)
SOURCES.md existstest -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}/

CheckHowPassFail
Audio dir exists (correct path)test -d {audio_root}/artists/{artist}/albums/{genre}/{album}[PASS] Audio directory: {path}See below
Audio dir in wrong locationtest -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}/
CheckHowPassSkip
WAV files presentls {audio_path}/*.wav[PASS] {N} WAV files found[SKIP] No audio files yet
mastered/ existstest -d {audio_path}/mastered[PASS] mastered/ directory exists[SKIP] Not mastered yet

ALBUM ART

ALBUM ART
─────────
CheckHowPassSkip
Art in audio foldertest -f {audio_path}/album.png[PASS] album.png in audio folder[SKIP] No album art yet
Art in content foldertest -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. ...

---

Example Output

═══════════════════════════════════════════════════════════
ALBUM VALIDATION: sample-album
═══════════════════════════════════════════════════════════

CONFIG
──────
[PASS] Config file exists
[PASS] content_root: ~/bitwize-music
[PASS] audio_root: ~/bitwize-music/audio
[PASS] artist: bitwize

ALBUM STRUCTURE
───────────────
[PASS] Album directory: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/
[PASS] README.md exists
[PASS] tracks/ directory exists
[PASS] 5 track files found

AUDIO FILES
───────────
[FAIL] Audio directory in wrong location
       → Expected: ~/bitwize-music/audio/artists/bitwize/albums/electronic/sample-album/
       → Found at: ~/bitwize-music/audio/sample-album/
       → Fix: mv ~/bitwize-music/audio/sample-album/ ~/bitwize-music/audio/artists/bitwize/albums/electronic/sample-album/

ALBUM ART
─────────
[SKIP] No album art yet

TRACKS
──────
[PASS] 01-intro.md - Status: Final, Suno Link: present
[PASS] 02-track.md - Status: Final, Suno Link: present
[WARN] 03-t-day-beach.md - Status: Generated, Suno Link: missing

═══════════════════════════════════════════════════════════
SUMMARY: 8 passed, 1 failed, 1 warning, 1 skipped
═══════════════════════════════════════════════════════════

ISSUES TO FIX:
1. Move audio folder to include artist:
   mv ~/bitwize-music/audio/sample-album/ ~/bitwize-music/audio/artists/bitwize/albums/electronic/sample-album/

---

Important Notes

1. Use MCP tools first - get_config(), find_album(), validate_album_structure() before manual checks 2. Check both correct AND wrong locations - Catch misplaced files 3. Provide actionable fixes - Include exact commands to fix issues 4. Use appropriate status - PASS/FAIL/WARN/SKIP based on severity 5. Count everything - Report totals in summary

Related skills

Release Managementautomationresearch

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.