MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Finds an album by name and shows detailed status with next steps.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills resume --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "resume" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resume into .claude/skills/resume/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resumeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills resume --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/resume .agents/skills/resume && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "resume" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resume into .agents/skills/resume/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills resume --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/resume .cursor/skills/resume && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "resume" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resume into .cursor/skills/resume/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills.git --path skills/resume--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills resume --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/resume .gemini/skills/resume && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "resume" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resume into .gemini/skills/resume/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bitwize-music-studio/claude-ai-music-skills resumeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/resume .github/skills/resume && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "resume" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resume into .github/skills/resume/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill resume -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills resume --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/resume .opencode/skills/resume && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "resume" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/resume into .opencode/skills/resume/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resume", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
resumeFinds 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. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobBashbitwize-music-mcpFrom allowed-tools in the SKILL.md frontmatter.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Read, Glob, Bash, bitwize-music-mcpAutomated 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.
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.
.claude/skills/resume/SKILL.md (or your agent's skills folder).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.
When this skill is invoked with an album name:
find_album(name) — fuzzy match by name, slug, or partial (case-insensitive)/bitwize-music:new-albumrebuild_state() then retryget_album_progress(album_slug) — returns track counts by status, completion percentage, and detected workflow phaselist_tracks(album_slug) — returns per-track details (status, has_suno_link, sources_verified)Call update_session(album=album_slug, phase=detected_phase) to set the active album and phase.
Based on album and track statuses, identify the workflow phase:
| Album Status | Track Statuses | Current Phase |
|---|---|---|
| Concept | Most "Not Started" | Planning - Need to fill in album README and create tracks |
| Research Complete | Some "Sources Pending" | Verification - Need human verification of sources (documentary albums) |
| Sources Verified | All sources verified | Ready to Write - Sources cleared, begin lyrics (documentary albums) |
| In Progress | Mixed, some "Not Started" | Writing - Need to complete lyrics (or route instrumental tracks to suno-engineer) |
| In Progress | Some "Sources Pending" | Verification - Need human verification of sources |
| In Progress | All have lyrics | Ready to Generate - Run Ready to Generate checkpoint |
| In Progress | Some "Generated" | Generating - Continue generating on Suno. Check Generation Logs for rejected tracks needing regeneration |
| In Progress | All "Generated", none "Final" | Review & Approve - Listen to generated tracks, mark keepers with ✓, regenerate rejected ones |
| Complete | All "Final" | Mastering - Ready to master audio |
| Released | All "Final" | Released - Album is live |
Note: Non-documentary albums skip Research Complete and Sources Verified — they go directly from Concept → In Progress.
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.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]If invoked without an album name:
get_session() — check last_album from session context, resume that albumlist_albums() to find all in-progress albums/bitwize-music:new-albumPresent 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]/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./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?/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.find_album, get_album_progress, list_tracks, update_session instead of reading state.json directlyUse 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
Just SKILL.md in skills/resume of bitwize-music-studio/claude-ai-music-skills.
Open the folder on GitHubat commit 58f32c2
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Resume this skillbitwize-music-studio/claude-ai-music-skills | 544 | — | ~2.6k | Automated safety check: Notes | CC0-1.0 | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills | 8.5k | 6 repos | ~3.2k | Automated safety check: Notes | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
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.
anthropics/claude-plugins-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.
warpdotdev/warp
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.
google-labs-code/stitch-skills
Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
bitwize-music-studio/claude-ai-music-skills
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases.
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.
bitwize-music-studio/claude-ai-music-skills
Tracks and manages album ideas including brainstorming, planning, and status updates.
bitwize-music-studio/claude-ai-music-skills
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard.
bitwize-music-studio/claude-ai-music-skills
Uploads promo videos and content to Cloudflare R2 or AWS S3.
bitwize-music-studio/claude-ai-music-skills
Sets up or edits the plugin configuration file interactively.
Works with
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.
Resume fits situations like: the user mentions an album name; wants to continue previous work.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.