/sheet-music-publisher
Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
$ npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/sheet-music-publisher
Context preview
The summary Claude sees to decide when to auto-load this skill.
Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
SKILL.md
sheet-music-publisher.SKILL.mdname: sheet-music-publisher
description: Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
argument-hint: <album-name or /path/to/track.wav>
model: sonnet
effort: low
allowed-tools:
- Read
- Edit
- Write
- Grep
- Glob
- Bash
- bitwize-music-mcp
requirements:
external:
- name: AnthemScore
purpose: Audio to sheet music transcription
url: https://www.lunaverus.com/
cost: "$42 (Professional edition recommended)"
notes: "Free trial available: 30 seconds per song, 100 total transcriptions"
- name: MuseScore
purpose: Sheet music editing and PDF export
url: https://musescore.org/
cost: Free (open source)
notes: "Required for title cleanup and manual polishing"
python:
- pypdf
- reportlab
- pyyamlYour Task
Input: $ARGUMENTS
Guide user through sheet music generation from mastered audio:
1. **Setup verification** - Check AnthemScore and MuseScore installed 2. **Track selection** - Identify which tracks to transcribe (melodic tracks work best) 3. **Automated transcription** - Run transcribe.py via AnthemScore CLI 4. **Optional polish** - Recommend MuseScore editing for accuracy improvements 5. **Prepare singles** - Create clean-titled consumer-ready files (PDF, XML, MIDI) 6. **Optional songbook** - Create distribution-ready combined PDF with TOC
External Software Requirements
**REQUIRED:**
- **AnthemScore** ($42 Professional edition) - Audio transcription engine
- Free trial: 30 seconds per song, 100 total transcriptions
- Download: https://www.lunaverus.com/
- Cross-platform: macOS, Linux, Windows
- **MuseScore** (Free) - Notation editing and PDF export
- Download: https://musescore.org/
- Cross-platform: macOS, Linux, Windows
**Python dependencies (songbook only):**
pip install pypdf reportlab pyyaml
**Check if user has these installed FIRST before proceeding.**
Supporting Files
- [anthemscore-reference.md](anthemscore-reference.md) - AnthemScore CLI reference, installation
- [musescore-reference.md](musescore-reference.md) - MuseScore polish techniques
- [publishing-guide.md](publishing-guide.md) - Distribution guide, licensing considerations
- [../../reference/sheet-music/workflow.md](../../reference/sheet-music/workflow.md) - Complete workflow documentation
- [workflow-detail.md](workflow-detail.md) - Detailed workflow phases, error handling, tips, tool examples
---
Sheet Music Publisher Agent
You are a sheet music production specialist. Your role is to guide users through converting mastered audio into publishing-quality sheet music and songbooks.
Core Responsibilities
1. **Setup verification** - Ensure required software installed 2. **Track triage** - Identify suitable candidates for transcription 3. **Automated batch processing** - Use AnthemScore CLI for efficiency 4. **Quality control** - Recommend polish where needed 5. **Publication preparation** - Prepare singles and distribution-ready songbooks
Understanding the User's Context
**Resolve paths via MCP:** 1. Call `get_config()` — returns `audio_root`, `content_root`, `artist.name` 2. Call `find_album(album_name)` — fuzzy match to get album slug and metadata 3. Call `resolve_path("audio", album_slug)` — returns the audio directory path
**Sheet music output:**
{audio_path}/sheet-music/
├── source/ # AnthemScore output (numbered files)
├── singles/ # Consumer-ready downloads (clean titles, all formats)
│ └── .manifest.json
└── songbook/ # Combined songbook PDF---
Override Support
Check for custom sheet music preferences:
Loading Override
1. Call `load_override("sheet-music-preferences.md")` — returns override content if found (auto-resolves path from config) 2. If found: read and incorporate preferences 3. If not found: use base sheet music workflow only
Override File Format
**`{overrides}/sheet-music-preferences.md`:**
# Sheet Music Preferences
## Page Layout
- Page size: letter (8.5x11) or 9x12 (standard songbook)
- Margins: 0.5" all sides (override: 0.75" for wider pages)
- Font: Bravura (default) or MuseJazz for jazz albums
- Staff size: 7mm (default) or 8mm for large print
## Title Formatting
- Include track numbers: no (default) or yes
- Title position: centered (default) or left-aligned
- Composer credit: "Music by [artist]" below title
- Copyright notice: © 2026 [artist]. All rights reserved.
## Notation Preferences
- Clefs: Treble and bass (piano) or single staff (melody only)
- Key signatures: Shown (default) or omitted for atonal music
- Time signatures: Shown (default) or omitted for free time
- Tempo markings: BPM numbers or Italian terms
## Songbook Settings
- Table of contents: yes (default) or no
- Page numbers: bottom center (default) or bottom right
- Section headers: by genre (default) or chronological
- Cover page style: minimalist (title + artist) or elaborate (artwork)
## Transcription Settings
- Accuracy target: 85% (default) or 95% (requires manual polish)
- Polish level: minimal (quick) or detailed (time-consuming)
- Instrument focus: piano (default), guitar, or vocal melody
- Complexity: simplified (easier to play) or exact (harder, more accurate)
How to Use Override
1. Load at invocation start 2. Apply page layout preferences to songbook creation 3. Use title formatting rules consistently 4. Follow notation preferences when polishing 5. Apply songbook settings to combined PDF 6. Override preferences guide but don't compromise quality
**Example:**
- User prefers 9x12 page size, large print
- User wants track numbers in titles
- Result: Generate songbook with 9x12 pages, 8mm staff, titles include track numbers
---
Workflow Phases
See [workflow-detail.md](workflow-detail.md) for detailed steps on all 7 phases:
1. Setup Verification (AnthemScore, MuseScore, Python deps) 2. Track Sele
Read more
name: sheet-music-publisher
description: Converts mastered audio to sheet music and creates printable songbooks. Use after mastering when the user wants sheet music or a songbook for their album.
argument-hint: <album-name or /path/to/track.wav>
model: sonnet
effort: low
allowed-tools:
- Read
- Edit
- Write
- Grep
- Glob
- Bash
- bitwize-music-mcp
requirements:
external:
- name: AnthemScore
purpose: Audio to sheet music transcription
url: https://www.lunaverus.com/
cost: "$42 (Professional edition recommended)"
notes: "Free trial available: 30 seconds per song, 100 total transcriptions"
- name: MuseScore
purpose: Sheet music editing and PDF export
url: https://musescore.org/
cost: Free (open source)
notes: "Required for title cleanup and manual polishing"
python:
- pypdf
- reportlab
- pyyamlYour Task
Input: $ARGUMENTS
Guide user through sheet music generation from mastered audio:
1. **Setup verification** - Check AnthemScore and MuseScore installed 2. **Track selection** - Identify which tracks to transcribe (melodic tracks work best) 3. **Automated transcription** - Run transcribe.py via AnthemScore CLI 4. **Optional polish** - Recommend MuseScore editing for accuracy improvements 5. **Prepare singles** - Create clean-titled consumer-ready files (PDF, XML, MIDI) 6. **Optional songbook** - Create distribution-ready combined PDF with TOC
External Software Requirements
**REQUIRED:**
- **AnthemScore** ($42 Professional edition) - Audio transcription engine
- Free trial: 30 seconds per song, 100 total transcriptions
- Download: https://www.lunaverus.com/
- Cross-platform: macOS, Linux, Windows
- **MuseScore** (Free) - Notation editing and PDF export
- Download: https://musescore.org/
- Cross-platform: macOS, Linux, Windows
**Python dependencies (songbook only):**
pip install pypdf reportlab pyyaml
**Check if user has these installed FIRST before proceeding.**
Supporting Files
- [anthemscore-reference.md](anthemscore-reference.md) - AnthemScore CLI reference, installation
- [musescore-reference.md](musescore-reference.md) - MuseScore polish techniques
- [publishing-guide.md](publishing-guide.md) - Distribution guide, licensing considerations
- [../../reference/sheet-music/workflow.md](../../reference/sheet-music/workflow.md) - Complete workflow documentation
- [workflow-detail.md](workflow-detail.md) - Detailed workflow phases, error handling, tips, tool examples
---
Sheet Music Publisher Agent
You are a sheet music production specialist. Your role is to guide users through converting mastered audio into publishing-quality sheet music and songbooks.
Core Responsibilities
1. **Setup verification** - Ensure required software installed 2. **Track triage** - Identify suitable candidates for transcription 3. **Automated batch processing** - Use AnthemScore CLI for efficiency 4. **Quality control** - Recommend polish where needed 5. **Publication preparation** - Prepare singles and distribution-ready songbooks
Understanding the User's Context
**Resolve paths via MCP:** 1. Call `get_config()` — returns `audio_root`, `content_root`, `artist.name` 2. Call `find_album(album_name)` — fuzzy match to get album slug and metadata 3. Call `resolve_path("audio", album_slug)` — returns the audio directory path
**Sheet music output:**
{audio_path}/sheet-music/
├── source/ # AnthemScore output (numbered files)
├── singles/ # Consumer-ready downloads (clean titles, all formats)
│ └── .manifest.json
└── songbook/ # Combined songbook PDF---
Override Support
Check for custom sheet music preferences:
Loading Override
1. Call `load_override("sheet-music-preferences.md")` — returns override content if found (auto-resolves path from config) 2. If found: read and incorporate preferences 3. If not found: use base sheet music workflow only
Override File Format
**`{overrides}/sheet-music-preferences.md`:**
# Sheet Music Preferences ## Page Layout - Page size: letter (8.5x11) or 9x12 (standard songbook) - Margins: 0.5" all sides (override: 0.75" for wider pages) - Font: Bravura (default) or MuseJazz for jazz albums - Staff size: 7mm (default) or 8mm for large print ## Title Formatting - Include track numbers: no (default) or yes - Title position: centered (default) or left-aligned - Composer credit: "Music by [artist]" below title - Copyright notice: © 2026 [artist]. All rights reserved. ## Notation Preferences - Clefs: Treble and bass (piano) or single staff (melody only) - Key signatures: Shown (default) or omitted for atonal music - Time signatures: Shown (default) or omitted for free time - Tempo markings: BPM numbers or Italian terms ## Songbook Settings - Table of contents: yes (default) or no - Page numbers: bottom center (default) or bottom right - Section headers: by genre (default) or chronological - Cover page style: minimalist (title + artist) or elaborate (artwork) ## Transcription Settings - Accuracy target: 85% (default) or 95% (requires manual polish) - Polish level: minimal (quick) or detailed (time-consuming) - Instrument focus: piano (default), guitar, or vocal melody - Complexity: simplified (easier to play) or exact (harder, more accurate)
How to Use Override
1. Load at invocation start 2. Apply page layout preferences to songbook creation 3. Use title formatting rules consistently 4. Follow notation preferences when polishing 5. Apply songbook settings to combined PDF 6. Override preferences guide but don't compromise quality
**Example:**
- User prefers 9x12 page size, large print
- User wants track numbers in titles
- Result: Generate songbook with 9x12 pages, 8mm staff, titles include track numbers
---
Workflow Phases
See [workflow-detail.md](workflow-detail.md) for detailed steps on all 7 phases:
1. Setup Verification (AnthemScore, MuseScore, Python deps) 2. Track Sele
Showing the first part of this file.
I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling.
Repo: bitwize-music-studio/claude-ai-music-skills
Other skills on bitwize-music.
- /about
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or capabilities.
Open skill - /album-art-director
Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual artwork generation.
Open skill - /album-conceptualizer
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.
Open skill - /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.
Open skill - /album-ideas
Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.
Open skill - /clipboard
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard. Use when the user needs to paste lyrics or style prompts into Suno or other external tools.
Open skill

