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.
- Installs
- 223
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill album-dashboard- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads album-dashboard automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
| Phase | Complete When |
|---|---|
| 1. Concept | Album README has title, genre, tracklist defined |
| 2. Research | RESEARCH.md and SOURCES.md exist (if source-based) |
| 3. Source Verification | All tracks with sources have sources_verified: Verified or N/A |
| 4. Lyrics | All tracks have lyrics in their Lyrics Box |
| 5. Pronunciation | All pronunciation table entries applied in lyrics |
| 6. Review | Lyrics reviewed (no critical issues remain) |
| 7. Generation | All tracks have has_suno_link: true |
| 8. Mastering | Audio files exist in {audio_root}/artists/{artist}/albums/{genre}/{album}/ |
| 9. Release | Album status is "Released" |
Data Collection
From MCP Server
- Call
get_album_progress(album_slug)— returns completion stats, phase detection, track counts by status - Call
find_album(name)— returns album metadata (genre, status, track list with per-track fields) - 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
- Visual progress bars — Use ASCII progress bars for quick scanning
- Highlight blockers — Blocking items are the most important info
- Include next action — End with a clear recommendation
- Be accurate — Count carefully, don't estimate
- Handle missing data gracefully — If audio_root doesn't exist, mastering is 0%
FAQ
What does the album-dashboard skill do?
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.
How do I install album-dashboard?
Run npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill album-dashboard in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/album-dashboard/ (personal) or .claude/skills/album-dashboard/ (project).
Which AI agents can use album-dashboard?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is album-dashboard safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains album-dashboard?
It is published by bitwize-music-studio in bitwize-music-studio/claude-ai-music-skills. It has 223 recorded installs.
More from bitwize-music-studio/claude-ai-music-skills
lyric-writer
bitwize-music-studio/claude-ai-music-skills
Writes or reviews lyrics with professional prosody, rhyme craft, and quality checks. Use when writing new lyrics, revising existing lyrics, or when the user says 'let's work on a track.'
suno-engineer
bitwize-music-studio/claude-ai-music-skills
Constructs technical Suno style prompts for the current model family (v6, v6-wild, v6-mini), selects models and generation settings, and optimizes prompts. Use when creating or refining Suno prompts for track generation.
plagiarism-checker
bitwize-music-studio/claude-ai-music-skills
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
mastering-engineer
bitwize-music-studio/claude-ai-music-skills
Guides audio mastering for streaming platforms including loudness optimization and tonal balance. Use when the user has approved tracks and wants to master audio files.
mix-engineer
bitwize-music-studio/claude-ai-music-skills
Polishes raw Suno audio by processing per-stem WAVs (vocals, backingvocals, drums, bass, guitar, keyboard, strings, brass, woodwinds, percussion, synth, other) with targeted cleanup, EQ, and compression, then remixing into a polished stereo WAV ready for mastering. Use after audio import and before mastering.
lyric-reviewer
bitwize-music-studio/claude-ai-music-skills
Open the skill to read its SKILL.md instructions.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.