Claude-ai-music-skills 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.
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/bitwize-music-studio/claude-ai-music-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/sheet-music-publisher" ~/.claude/skills/bitwize-music-studio-claude-ai-music-skills-sheet-music-publisher && rm -rf "$T"
skills/sheet-music-publisher/SKILL.mdYour Task
Input: $ARGUMENTS
Guide user through sheet music generation from mastered audio:
- Setup verification - Check AnthemScore and MuseScore installed
- Track selection - Identify which tracks to transcribe (melodic tracks work best)
- Automated transcription - Run transcribe.py via AnthemScore CLI
- Optional polish - Recommend MuseScore editing for accuracy improvements
- Prepare singles - Create clean-titled consumer-ready files (PDF, XML, MIDI)
- 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 CLI reference, installation
- musescore-reference.md - MuseScore polish techniques
- publishing-guide.md - Distribution guide, licensing considerations
- ../../reference/sheet-music/workflow.md - Complete workflow documentation
- 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
- Setup verification - Ensure required software installed
- Track triage - Identify suitable candidates for transcription
- Automated batch processing - Use AnthemScore CLI for efficiency
- Quality control - Recommend polish where needed
- Publication preparation - Prepare singles and distribution-ready songbooks
Understanding the User's Context
Resolve paths via MCP:
- Call
— returnsget_config()
,audio_root
,content_rootartist.name - Call
— fuzzy match to get album slug and metadatafind_album(album_name) - Call
— returns the audio directory pathresolve_path("audio", album_slug)
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
- Call
— returns override content if found (auto-resolves path from config)load_override("sheet-music-preferences.md") - If found: read and incorporate preferences
- 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
- Load at invocation start
- Apply page layout preferences to songbook creation
- Use title formatting rules consistently
- Follow notation preferences when polishing
- Apply songbook settings to combined PDF
- 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 for detailed steps on all 7 phases:
- Setup Verification (AnthemScore, MuseScore, Python deps)
- Track Selection
- Automated Transcription (outputs to source/)
- Quality Review & Polish
- Prepare Singles (clean titles → singles/)
- Songbook Creation (optional → songbook/)
- Summary & Next Steps
Also covers: Error Handling, Tips for Better Results, Tool Invocation Examples, Quality Standards, Workflow State Tracking.
Remember
- Load override first - Call
at invocationload_override("sheet-music-preferences.md") - Apply formatting preferences - Use override page layout, notation, songbook settings if available
- Use MCP for paths - Call
,get_config()
,find_album()
instead of reading config manuallyresolve_path("audio") - Check software exists - Graceful failure with install instructions
- Set expectations - 70-95% accuracy, may need polish
- Offer polish - Don't skip this step
- Automate what you can - Use CLI tools, minimize manual work
- 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