Finds an album by name and shows detailed status with next steps.

CC0-1.0Auto-check: notes

Install Resume

skills CLI
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitwize-music-studio/claude-ai-music-skills resume --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/resume .claude/skills/resume && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
resume
GitHub stars
544
Token cost
~2.6k tokens
SKILL.md length
544 words
Files
1
Skills in repo
51
Repo updated
First seen
Licence
CC0-1.0

At a glance

Finds an album by name and shows detailed status with next steps.

  • Works in 6 steps: Find the Album via MCP → Get Album Progress → Update Session Context → …
  • The user mentions an album name
  • SKILL.md covers Instructions, Examples, Implementation Notes and Model
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Resume is an agent skill from bitwize-music-studio/claude-ai-music-skills. Finds an album by name and shows detailed status with next steps. Use when the user mentions an album name or wants to continue previous work.

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Model Context Protocol and Suno. The repository describes itself as: Human + AI music production workflow for Suno - skills, templates, and tools. The licence is CC0-1.0.

When your agent uses it

  • The user mentions an album name
  • Wants to continue previous work

Example prompts

  • “Use the resume skill to find an album by name and shows detailed status with next steps”
  • “/resume”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Bash, bitwize-music-mcp

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Find the Album via MCP
  2. Get Album Progress
  3. Update Session Context
  4. Determine Current Phase
  5. Report to User
  6. Recommend the Single Best Next Action

What it can do on your machine

Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Bash
    • bitwize-music-mcp

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Resume loads about 2.6k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 544 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Bash, bitwize-music-mcp

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitwize-music-studio/claude-ai-music-skills at commit 58f32c2, republished under its CC0-1.0 licence (© bitwize-music-studio). 544 words, ~2,607 tokens.

Download SKILL.mdSave it as .claude/skills/resume/SKILL.md (or your agent's skills folder).
name
resume
description
Finds an album by name and shows detailed status with next steps. Use when the user mentions an album name or wants to continue previous work.
allowed-tools
Read, Glob, Bash, bitwize-music-mcp
argument-hint
<album-name>
model
sonnet
effort
low

Resume Album Work

Purpose: Find an album and resume work where you left off.

Usage:

/bitwize-music:resume <album-name>
/bitwize-music:resume my-album
/bitwize-music:resume "demo album"

When to use: When user wants to continue working on an existing album.


Instructions

When this skill is invoked with an album name:

Step 1: Find the Album via MCP
  1. Call find_album(name) — fuzzy match by name, slug, or partial (case-insensitive)
  2. If not found: MCP returns available albums — suggest closest match or /bitwize-music:new-album
  3. If multiple matches: list all with paths, ask user which one
  4. If MCP returns stale/missing cache error: call rebuild_state() then retry
Step 2: Get Album Progress
  1. Call get_album_progress(album_slug) — returns track counts by status, completion percentage, and detected workflow phase
  2. Call list_tracks(album_slug) — returns per-track details (status, has_suno_link, sources_verified)
Step 3: Update Session Context

Call update_session(album=album_slug, phase=detected_phase) to set the active album and phase.

Step 4: Determine Current Phase

Based on album and track statuses, identify the workflow phase:

Album StatusTrack StatusesCurrent Phase
ConceptMost "Not Started"Planning - Need to fill in album README and create tracks
Research CompleteSome "Sources Pending"Verification - Need human verification of sources (documentary albums)
Sources VerifiedAll sources verifiedReady to Write - Sources cleared, begin lyrics (documentary albums)
In ProgressMixed, some "Not Started"Writing - Need to complete lyrics (or route instrumental tracks to suno-engineer)
In ProgressSome "Sources Pending"Verification - Need human verification of sources
In ProgressAll have lyricsReady to Generate - Run Ready to Generate checkpoint
In ProgressSome "Generated"Generating - Continue generating on Suno. Check Generation Logs for rejected tracks needing regeneration
In ProgressAll "Generated", none "Final"Review & Approve - Listen to generated tracks, mark keepers with ✓, regenerate rejected ones
CompleteAll "Final"Mastering - Ready to master audio
ReleasedAll "Final"Released - Album is live

Note: Non-documentary albums skip Research Complete and Sources Verified — they go directly from Concept → In Progress.

Step 5: Report to User

Present a clear status report:

📁 Album: [Album Title]
   Location: {content_root}/artists/{artist}/albums/{genre}/{album}/
   Status: [Album Status]

📊 Progress:
   - Tracks: [X completed / Y total] ([N vocal, M instrumental])
   - Not Started: X
   - In Progress: Y
   - Generated: Z
   - Final: N

📍 Current Phase: [Phase Name]

✅ What's Done:
   - [List completed items]

⏭️ Next Steps:
   1. [Specific action 1]
   2. [Specific action 2]
   3. [Specific action 3]

Ready to continue? Tell me what you'd like to work on.
Show full SKILL.md (230 more words)Show less
Step 6: Recommend the Single Best Next Action

Pick ONE clear recommendation from the decision tree below. Don't list 5 options — pick the best one, include the skill name, and be specific about which track.

Decision Tree (evaluate top-to-bottom, first match wins):

Instrumental detection: Check each track's frontmatter for instrumental: true or Track Details table for **Instrumental** | Yes. Instrumental tracks skip the lyrics workflow entirely and go straight to /bitwize-music:suno-engineer.

Album Status = "Concept"
  → "Define the album concept. Run /bitwize-music:album-conceptualizer"

Album Status = "Research Complete"
  → Any tracks Sources Pending?
    YES → "Sources need verification. Run /bitwize-music:verify-sources [album]"
    NO  → Any "Not Started" tracks instrumental?
      YES → "Create Style Box for instrumental track [name]. Use /bitwize-music:suno-engineer"
      NO  → "Ready to write! Pick a track and use /bitwize-music:lyric-writer"

Album has tracks with "Not Started"
  → Is the first not-started track instrumental?
    YES → "Create Style Box for [track]. Use /bitwize-music:suno-engineer directly (instrumental track)"
    NO  → "Write lyrics for [first not-started track]. Use /bitwize-music:lyric-writer"

Album has tracks with "In Progress" (lyrics partially written)
  → "Finish lyrics for [first in-progress track]. Use /bitwize-music:lyric-writer"

Album has tracks with "Sources Pending"
  → "Verify sources for [track]. Run /bitwize-music:verify-sources [album]"

All tracks have lyrics (or Style Box for instrumentals), none generated
  → Mixed album (vocal + instrumental)?
    YES → "All tracks ready! Run /bitwize-music:pronunciation-specialist on vocal tracks, then /bitwize-music:lyric-reviewer, then /bitwize-music:pre-generation-check to validate all gates (instrumental tracks auto-skip lyrics gates)."
    NO  → "All lyrics complete! Style prompts should be ready. Run /bitwize-music:pronunciation-specialist to check for pronunciation risks, then /bitwize-music:lyric-reviewer for final QC, then /bitwize-music:pre-generation-check to validate all gates before generating on Suno."

Some tracks generated, some not
  → Any Generated tracks without ✓ in Generation Log Rating?
    YES → "Track [name] was generated but not approved. Listen and decide:
           - Happy? Mark ✓ in Generation Log and set Status: Final
           - Not happy? Log the reason, then:
             Style issue → /bitwize-music:suno-engineer to revise Style Box
             Lyrics issue → /bitwize-music:lyric-writer to fix, then regenerate
             Bad luck → Regenerate on Suno with same settings (it's non-deterministic)"
    NO  → "Generate [first un-generated track] on Suno. Use /bitwize-music:suno-engineer"

All tracks generated, none Final
  → "All tracks generated! Listen to each track and approve:
     - Mark keepers with ✓ in Generation Log Rating column
     - Reject and regenerate any that don't meet quality standards
     - Once all have ✓, batch-approve:
       Use update_track_field(album_slug, track_slug, 'status', 'Final') for each approved track.
       Once all Final, album advances to Complete automatically."

All tracks generated, some Final
  → Any Generated (non-Final) tracks without ✓?
    YES → "Review track [name] — listen and approve (✓) or regenerate"
    NO  → "All tracks approved! Batch-approve: update_track_field(album_slug, track_slug, 'status', 'Final') for each.
           Then import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"

All tracks Final
  → "All tracks approved! Import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"

Album Status = "Complete"
  → "Album is complete! Release with /bitwize-music:release-director"

Album Status = "Released"
  → "This album is released! Consider /bitwize-music:promo-director for promotional content"
  → Also suggest: "Start a new album? Check /bitwize-music:album-ideas list"

Format the recommendation as:

RECOMMENDED NEXT ACTION:
  [Clear, specific instruction with skill name and track name]

WHY:
  [One sentence explaining why this is the right next step]
When No Album Specified (No Arguments)

If invoked without an album name:

  1. Call get_session() — check last_album from session context, resume that album
  2. If no session context, call list_albums() to find all in-progress albums
  3. Prioritize: closest to completion > unblocked work > last worked on
  4. If no albums exist, suggest /bitwize-music:new-album

Present a multi-album summary if multiple are in progress:

You have X albums. Here's the most actionable:

PRIORITY 1: [album-name] ([genre])
  Status: [status] | Progress: [X/Y tracks]
  → [Recommended action]

Also in progress:
  - [album-2] — [brief status]

Examples

Example 1: Album in Writing Phase
/bitwize-music:resume my-album

📁 Album: My Album
   Location: ~/bitwize-music/artists/bitwize/albums/rock/my-album/
   Status: In Progress

📊 Progress:
   - Tracks: 3 completed / 8 total
   - Not Started: 3
   - In Progress: 2
   - Final: 3

📍 Current Phase: Writing Lyrics

✅ What's Done:
   - Tracks 1-3 have final lyrics
   - Album concept and tracklist defined

⏭️ Next Steps:
   1. Complete lyrics for Track 4 (in progress)
   2. Complete lyrics for Track 5 (in progress)
   3. Write lyrics for Tracks 6-8

Ready to continue? Tell me which track you'd like to work on.
Example 2: Album Ready for Generation
/bitwize-music:resume demo-album

📁 Album: Demo Album
   Location: ~/bitwize-music/artists/bitwize/albums/electronic/demo-album/
   Status: In Progress

📊 Progress:
   - Tracks: 8 / 8 total (all lyrics complete)
   - Final: 8

📍 Current Phase: Ready to Generate

✅ What's Done:
   - All 8 tracks have complete lyrics
   - All lyrics phonetically reviewed
   - Suno Style and Lyrics boxes filled

⏭️ Next Steps:
   1. Run Ready to Generate checkpoint (I'll verify everything)
   2. Start generating on Suno
   3. Log generation attempts

Shall I run the Ready to Generate checkpoint now?
Example 3: Album Not Found
/bitwize-music:resume my-album

❌ Album 'my-album' not found.

Available albums:
- demo-album (electronic) - In Progress
- example-tracks (hip-hop) - Complete

Did you mean one of these? Or use /bitwize-music:new-album to create a new album.

Implementation Notes

  • Use MCP tools - find_album, get_album_progress, list_tracks, update_session instead of reading state.json directly
  • Case-insensitive matching - "Sample-Album" should match "sample-album"
  • Handle missing albums gracefully - List what exists, don't error
  • Be specific about next steps - Don't just say "continue working", say exactly what to do
  • Include full paths - User needs to know where files are located
  • Use emojis sparingly - Only for section headers in the report

Model

Use Sonnet 4.5 - This is a coordination/reporting task, not creative work.

© bitwize-music-studio, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/resume of bitwize-music-studio/claude-ai-music-skills.

Open the folder on GitHubat commit 58f32c2

Compare with similar skills

Resume next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Resume compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Resume this skillbitwize-music-studio/claude-ai-music-skills544—~2.6kAutomated safety check: NotesCC0-1.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.5k6 repos~3.2kAutomated safety check: NotesApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.5k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes
  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

More from bitwize-music-studio/claude-ai-music-skills

All 51 skills in this repo
  • Album Conceptualizer

    bitwize-music-studio/claude-ai-music-skills

    Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases.

    544 GitHub stars~3.6k tokensUpdated 2 days ago
    Auto-check passed
  • Album Dashboard

    bitwize-music-studio/claude-ai-music-skills

    Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown.

    544 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Album Ideas

    bitwize-music-studio/claude-ai-music-skills

    Tracks and manages album ideas including brainstorming, planning, and status updates.

    544 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed
  • Clipboard

    bitwize-music-studio/claude-ai-music-skills

    Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard.

    544 GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check: notes
  • Cloud Uploader

    bitwize-music-studio/claude-ai-music-skills

    Uploads promo videos and content to Cloudflare R2 or AWS S3.

    544 GitHub stars~2.1k tokensUpdated 2 days ago
    Auto-check: notes
  • Configure

    bitwize-music-studio/claude-ai-music-skills

    Sets up or edits the plugin configuration file interactively.

    544 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check: notes

Questions about Resume

What does Resume do?

Finds an album by name and shows detailed status with next steps. Resume is an agent skill from bitwize-music-studio/claude-ai-music-skills. Finds an album by name and shows detailed status with next steps.

When should I use Resume?

Resume fits situations like: the user mentions an album name; wants to continue previous work.

How do I install Resume in Claude Code?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a claude-code`. Or copy the skill folder (skills/resume in bitwize-music-studio/claude-ai-music-skills) into .claude/skills/resume in your project. Claude Code loads it when a task matches its description.

How do I install Resume in Codex?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a codex`. Or copy the skill folder (skills/resume in bitwize-music-studio/claude-ai-music-skills) into .agents/skills/resume in your project. Codex loads it when a task matches its description.

Can I use Resume in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resume, .gemini/skills/resume, .github/skills/resume and .opencode/skills/resume in your project.

What does Resume need to run?

SKILL.md names no scripts, command-line tools or credentials: Resume is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Bash, bitwize-music-mcp.

Does Resume access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Resume safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Resume use?

Resume is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Resume use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Resume?

Skills that share tags, products or a category with Resume: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Resume?

bitwize-music-studio (a GitHub organization) maintains it in bitwize-music-studio/claude-ai-music-skills, which has 544 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 7, 2026.

Source: bitwize-music-studio/claude-ai-music-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.