Album Dashboard
Per-phase progress dashboard for a music album: percentages, blockers, next action
Fungerar med konfiguration
Vad den gör
Renders a nine-phase progress dashboard for an album in the bitwize-music workspace — concept, research, source verification, lyrics, pronunciation, review, generation, mastering, release — with ASCII progress bars, a per-track status table and a list of blocking items. It pulls album and track state from the plugin's bitwize-music MCP server (get_album_progress, find_album, list_track_files) and fills the remaining phases from files on disk. Triggers when you ask how far along an album is, what is blocking it, or for a status overview of every track.
Testrapport
I built a mock workspace (album "Neon Ledger", 6 tracks, 2 mastered WAVs, RESEARCH.md but no SOURCES.md, one track with unapplied pronunciation entries) under a temp HOME with ~/.bitwize-music/config.yaml, then ran the plugin's own indexer and called the three MCP handlers the skill depends on directly in Python: get_album_progress returned {"phase":"Source Verification","track_count":6,"tracks_completed":2,"completion_percentage":33.3,"sources_pending":3}, and find_album/list_track_files returned per-track status, has_suno_link and sources_verified. The baseline artifact reported that single 33.3% figure plus a track table and a one-line next step; the skill artifact reported nine phase percentages and caught three things the baseline never looked for — track 04's pronunciation entries (SWIFT, Nauru) present in the table but absent from the Lyrics Box, tracks 05/06 with placeholder Lyrics Box text, and the missing SOURCES.md (research at 50%) — plus Mastered 33% derived from counting audio files and Source Verification 40% by excluding the N/A track from the denominator. Docs lose a point because SKILL.md claims the three MCP calls "replace all manual state.json reads and file globbing", which the observed JSON payloads disprove (lyrics, pronunciation, audio files and RESEARCH/SOURCES all still need file reads), and the Review phase has no defined data source. Install verified by cloning into a fresh mktemp HOME — SKILL.md lands at ~/.claude/skills/album-dashboard/SKILL.md; no curl|sh, base64 or secret-exfil patterns in the skill. Trigger 5/5: would load on "show me the progress dashboard for the neon-ledger album", "how far along is my album — give me a per-phase breakdown of what's blocking", "what's blocking the Neon Ledger release, I want a status overview of every track"; would not load on "add a progress bar component to my React dashboard page" or "write lyrics for track 3 of Neon Ledger".
Testad: 2026-07-21 · Claude Code 2.x (agent harness)
Installation
git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git /tmp/album-dashboard-src
mkdir -p ~/.claude/skills
cp -R /tmp/album-dashboard-src/skills/album-dashboard ~/.claude/skills/album-dashboard
# The skill body calls MCP tools (get_album_progress, find_album, list_track_files) that only exist
# when the whole bitwize-music plugin is installed. For a working setup use the plugin route:
# /plugin marketplace add bitwize-music-studio/claude-ai-music-skills
# /plugin install bitwize-music@bitwize-music
# /bitwize-music:setup # Python 3.11+ deps for the MCP server (mcp[cli], pyyaml)
# /bitwize-music:configure # writes ~/.bitwize-music/config.yaml (artist name, content_root, audio_root)
# Then run: /bitwize-music:album-dashboard <album-name>
# Requires an album workspace at {content_root}/artists/{artist}/albums/{genre}/{album}/ with
# README.md + tracks/*.md; with no workspace the dashboard has nothing to read. Kommandon och exempelprompter
/album-dashboardPer-phase progress dashboard for a music album: percentages, blockers, next action
Skills triggas av vanliga förfrågningar — inga kommandon att memorera. Efter installationen aktiverar prompter som dessa skillen (på engelska):
Show my album progress dashboardWhat percentage of the album is completeList the blocking items on my album project