sheet-music-publisher
Skill589 starsChanged 9 months agoCC0-1.0View on GitHub
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.
- Installs packages
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 13 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Setup verification: - Check AnthemScore and MuseScore installed
- Very specific: line 41
Automated transcription: - Run transcribe.py via AnthemScore CLI
- Distinctive: line 43
Prepare singles: - Create clean-titled consumer-ready files (PDF, XML, MIDI)
- Distinctive: line 44
Optional songbook: - Create distribution-ready combined PDF with TOC
- Distinctive: line 81
Setup verification: - Ensure required software installed
- Distinctive: line 83
Automated batch processing: - Use AnthemScore CLI for efficiency
- Very specific: line 90
Call get_config() — returns audio_root, content_root, artist.name
- Very specific: line 91
Call find_album(album_name) — fuzzy match to get album slug and metadata
- Very specific: line 92
Call resolve_path("audio", album_slug) — returns the audio directory path
- Distinctive: line 107
Check for custom sheet music preferences:
- Very specific: line 111
Call load_override("sheet-music-preferences.md") — returns override content if found (auto-resolves path from config)
- Distinctive: line 112
If found: read and incorporate preferences
- Distinctive: line 113
If not found: use base sheet music workflow only
- Distinctive: line 156
Use title formatting rules consistently
- Distinctive: line 157
Follow notation preferences when polishing
- Very specific: line 185
Load override first: - Call load_override("sheet-music-preferences.md") at invocation
- Distinctive: line 186
Apply formatting preferences: - Use override page layout, notation, songbook settings if available
- Very specific: line 187
Use MCP for paths: - Call get_config(), find_album(), resolve_path("audio") instead of reading config manually
- Distinctive: line 190
Offer polish: - Don't skip this step
- Distinctive: line 191
Automate what you can: - Use CLI tools, minimize manual work
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Your 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 pyyamlCheck 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
get_config()— returnsaudio_root,content_root,artist.name - Call
find_album(album_name)— fuzzy match to get album slug and metadata - 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 PDFOverride Support
Check for custom sheet music preferences:
Loading Override
- Call
load_override("sheet-music-preferences.md")— returns override content if found (auto-resolves path from config) - 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
load_override("sheet-music-preferences.md")at invocation - Apply formatting preferences - Use override page layout, notation, songbook settings if available
- Use MCP for paths - Call
get_config(),find_album(),resolve_path("audio")instead of reading config manually - 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
In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- aboutSkill
- album-art-directorSkill
- album-conceptualizerSkill
- album-dashboardSkill
- album-ideasSkill
- clipboardSkill
- cloud-uploaderSkill
- configureSkill
- document-hunterSkill
- explicit-checkerSkill
- genre-creatorSkill
- health-checkSkill
- helpSkill
- import-artSkill
- import-audioSkill
- import-trackSkill
- lyric-refinerSkill
- lyric-reviewerSkill
- lyric-writerSkill
- mastering-engineerSkill
- mix-engineerSkill
- new-albumSkill
- next-stepSkill
- plagiarism-checkerSkill
- pre-generation-checkSkill
- promo-directorSkill
- promo-reviewerSkill
- promote-ideaSkill
- promo-writerSkill
- pronunciation-specialistSkill
- release-directorSkill
- renameSkill
- researchers-biographicalSkill
- researchers-financialSkill
- researchers-govSkill
- researchers-historicalSkill
- researchers-journalismSkill
- researcherSkill
- researchers-legalSkill
- researchers-primary-sourceSkill
- researchers-securitySkill
- researchers-techSkill
- researchers-verifierSkill
- resumeSkill
- session-startSkill
- setupSkill
- suno-engineerSkill
- testSkill
- tutorialSkill
- validate-albumSkill
- verify-sourcesSkill
- voice-checkerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

