Back to Skills

album-dashboard

bitwize-music-studio
Updated 2 days ago
3 views
209
37
209
View on GitHub
Designdesign

About

The album-dashboard skill generates a structured progress report for a specified music album, showing completion percentages per workflow phase, blocking items, and a status breakdown. It's designed to give developers a quick visual overview of album progress by reading project files and using the bitwize-music-mcp tool. Use this skill for a concise, actionable snapshot of where an album stands in its development lifecycle.

Quick Install

Claude Code

Recommended
Primary
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git CloneAlternative
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/album-dashboard

Copy and paste this command in Claude Code to install this skill

Documentation

Your Task

Input: $ARGUMENTS (album name)

Generate a structured progress dashboard for the specified album.


Album Dashboard

You generate a comprehensive progress report for an album, showing completion percentage per workflow phase, blocking items, and a structured status breakdown.


Workflow Phases

Track completion across these phases:

PhaseComplete When
1. ConceptAlbum README has title, genre, tracklist defined
2. ResearchRESEARCH.md and SOURCES.md exist (if source-based)
3. Source VerificationAll tracks with sources have sources_verified: Verified or N/A
4. LyricsAll tracks have lyrics in their Lyrics Box
5. PronunciationAll pronunciation table entries applied in lyrics
6. ReviewLyrics reviewed (no critical issues remain)
7. GenerationAll tracks have has_suno_link: true
8. MasteringAudio files exist in {audio_root}/artists/{artist}/albums/{genre}/{album}/
9. ReleaseAlbum status is "Released"

Data Collection

From MCP Server

  1. Call get_album_progress(album_slug) — returns completion stats, phase detection, track counts by status
  2. Call find_album(name) — returns album metadata (genre, status, track list with per-track fields)
  3. Call list_track_files(album_slug) — returns tracks with file paths for any additional checks

These three calls replace all manual state.json reads and file globbing.


Dashboard Format

ALBUM DASHBOARD
===============

[Album Title] ([genre])
Status: [status]

PROGRESS BY PHASE
─────────────────
[============================  ] 90%  Concept
[============================  ] 90%  Research
[========================      ] 75%  Source Verification
[====================          ] 63%  Lyrics Written
[================              ] 50%  Pronunciation
[============                  ] 38%  Reviewed
[========                      ] 25%  Generated
[                              ]  0%  Mastered
[                              ]  0%  Released

OVERALL: ████████░░░░░░░░ 47% complete

TRACK STATUS BREAKDOWN
──────────────────────
| # | Track | Status | Suno | Sources |
|---|-------|--------|------|---------|
| 01 | Track One | Final | link | Verified |
| 02 | Track Two | In Progress | — | Pending |
| 03 | Track Three | Not Started | — | N/A |
...

BLOCKING ITEMS
──────────────
! Track 02: Sources pending verification — blocks generation
! Track 05: No style prompt — blocks generation
! Track 07: Pronunciation table not applied — blocks generation

SUMMARY
───────
Tracks: [X complete / Y total]
Blocking: [N items]
Next action: [recommendation]

Phase Completion Calculation

Concept Phase

  • 100% if: Album README has title AND tracklist with actual track names (not template)
  • 50% if: README exists but tracklist is template placeholder
  • 0% if: No README

Research Phase (source-based albums only)

  • 100% if: RESEARCH.md AND SOURCES.md both exist with content
  • 50% if: Only one exists
  • N/A if: Album is not source-based (no tracks have sources_verified field or all are N/A)

Source Verification Phase

  • % = (tracks with Verified or N/A) / total tracks * 100
  • Skip tracks where sources_verified is N/A for the denominator

Lyrics Phase

  • % = (tracks with lyrics content) / total tracks * 100

Generation Phase

  • % = (tracks with has_suno_link=true) / total tracks * 100

Mastering Phase

  • Check {audio_root}/artists/{artist}/albums/{genre}/{album}/ for WAV/FLAC files
  • % = (audio files found) / total tracks * 100

Release Phase

  • 100% if album status is "Released", 0% otherwise

Remember

  1. Visual progress bars — Use ASCII progress bars for quick scanning
  2. Highlight blockers — Blocking items are the most important info
  3. Include next action — End with a clear recommendation
  4. Be accurate — Count carefully, don't estimate
  5. Handle missing data gracefully — If audio_root doesn't exist, mastering is 0%

GitHub Repository

bitwize-music-studio/claude-ai-music-skills
Path: skills/album-dashboard
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin

Related Skills

executing-plans

Design

Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.

View skill

requesting-code-review

Design

This skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.

View skill

connect-mcp-server

Design

This skill provides a comprehensive guide for developers to connect MCP servers to Claude Code using HTTP, stdio, or SSE transports. It covers installation, configuration, authentication, and security for integrating external services like GitHub, Notion, and custom APIs. Use it when setting up MCP integrations, configuring external tools, or working with Claude's Model Context Protocol.

View skill

web-cli-teleport

Design

This skill helps developers choose between Claude Code Web and CLI interfaces based on task analysis, then enables seamless session teleportation between these environments. It optimizes workflow by managing session state and context when switching between web, CLI, or mobile. Use it for complex projects requiring different tools at various stages.

View skill