sheet-music-publisher — Claude Code skill: output and setup
sheet-music-publisher turns mastered audio into notation and printable songbooks. Use it after album mastering when you need PDF, XML, MIDI, or a combined book.
CC0-1.0 270 installs ★ 686 updated 2026-10-22
npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a claude-codeWhat sheet-music-publisher does
This skill guides an audio-to-notation workflow from environment checks to publication files. It helps select tracks, run transcription through the AnthemScore CLI, review the result, and send it to MuseScore for manual cleanup when needed. Melodic material is the better fit.
Single-track deliverables include PDF, XML, and MIDI files with cleaned titles. An optional songbook combines the material into one PDF with a table of contents; that step uses the Python packages pypdf, reportlab, and pyyaml. Album and audio paths are resolved through bitwize-music-mcp.
AnthemScore and MuseScore are required for the workflow to run. AnthemScore handles transcription, while MuseScore is used for notation edits and PDF export. Automated notation may still need manual polishing.
What it helps with
- turn mastered audio into notation
- select tracks suited to transcription
- prepare publication-ready PDF, XML, and MIDI files
- combine tracks into a songbook PDF with a table of contents
- polish transcribed notation in MuseScore
Example prompts for the agent
- Convert
<album-name or /path/to/track.wav>into sheet music and prepare the files for publication. - Check the setup, choose melodic tracks, and run transcription with the AnthemScore CLI.
- Combine the album’s notation into one PDF songbook with a table of contents.
How to install sheet-music-publisher
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a claude-code2Manually: put the files in place
~/.claude/skills/sheet-music-publisher/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sheet-music-publisher/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a codex2Manually: put the files in place
.agents/skills/sheet-music-publisher/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a cursor2Manually: put the files in place
.cursor/skills/sheet-music-publisher/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bitwize-music-studio/claude-ai-music-skills skills/sheet-music-publisher2Manually: put the files in place
.github/skills/sheet-music-publisher/SKILL.md1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a gemini-cli2Platform CLI
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/sheet-music-publisherManually: put the files in place
.devin/skills/sheet-music-publisher/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sheet-music-publisher
How do I install sheet-music-publisher in Claude Code?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill sheet-music-publisher -a claude-code, then open ~/.claude/skills/sheet-music-publisher/SKILL.md.
What does sheet-music-publisher do?
It converts mastered audio into notation, prepares individual PDF, XML, and MIDI files, and can combine them into a printable songbook PDF.
What does sheet-music-publisher require?
AnthemScore is needed for transcription and MuseScore for notation editing and PDF export. Songbook generation also uses pypdf, reportlab, and pyyaml.
Source text
SKILL.md · CC0-1.0
---
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
- pyyaml
---
## Your 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):**
```bash
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`:**
```markdown
# 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 Selection
3. Automated Transcription (outputs to source/)
4. Quality Review & Polish
5. Prepare Singles (clean titles → singles/)
6. Songbook Creation (optional → songbook/)
7. Summary & Next Steps
Also covers: Error Handling, Tips for Better Results, Tool Invocation Examples, Quality Standards, Workflow State Tracking.
## Remember
1. **Load override first** - Call `load_override("sheet-music-preferences.md")` at invocation
2. **Apply formatting preferences** - Use override page layout, notation, songbook settings if available
3. **Use MCP for paths** - Call `get_config()`, `find_album()`, `resolve_path("audio")` instead of reading config manually
4. **Check software exists** - Graceful failure with install instructions
5. **Set expectations** - 70-95% accuracy, may need polish
6. **Offer polish** - Don't skip this step
7. **Automate what you can** - Use CLI tools, minimize manual work
8. **distribution-ready output** - Songbook should be upload-ready (with user preferences applied)
## Success Criteria
User should end with:
- ✓ Individual PDFs for each track (publishing-ready)
- ✓ MusicXML sources (editable in MuseScore)
- ✓ MIDI files for each track (playback)
- ✓ Optional: Combined songbook PDF (distribution-ready)
- ✓ Clear next steps for website distribution
- ✓ Understanding of quality level and polish needs
© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills