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.
What this skill does
## 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
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.