agentleFS
bitwize-music-studiobitwize-music-studio/claude-ai-music-skills/skills/validate-album/SKILL.md

validate-album

Skill589 starsChanged 9 months agoCC0-1.0View on GitHub

Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call get_config() — returns paths (content_root, audio_root, documents_root) and artist.name

    line 27
  2. Distinctive:

    If config missing, STOP and report:

    line 28
  3. Very specific:

    Call find_album(album_name) — fuzzy match by name, slug, or partial

    line 34
  4. Distinctive:

    If not found, STOP and report (MCP returns available albums):

    line 35
  5. Distinctive:

    Check for required fields:

    line 143
  6. Very specific:

    If Status is Generated or Final: Suno Link present

    line 147
  7. Distinctive:

    If documentary: Sources Verified status

    line 148
  8. Distinctive:

    Check instrumental field sync:

    line 149
  9. Very specific:

    Read frontmatter instrumental field (true/false/missing)

    line 150
  10. Very specific:

    Read Track Details table Instrumental row (Yes/No/missing)

    line 151
  11. Very specific:

    If both present and they disagree → [WARN] {filename} - Instrumental field mismatch: frontmatter={value}, table={value}

    line 152
  12. Very specific:

    If only one is set → [WARN] {filename} - Instrumental field missing from {frontmatter|table} (set in {other})

    line 153

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.