psr-sx-song-sheetslisted

Build a printable PDF song sheet for a Yamaha PSR-SX arranger keyboard (SX600 / SX700 / SX900) — scale with a rendered keyboard diagram, chords with their tones, a verified panel setup (style, voices, effects, Live Control, Registration slot), and full three-line notation with chord hits marked. Researches the song's key, tempo, chords and melody, reconciles disagreeing sources, and scores its own coverage rather than inventing what it could not verify; every preset name is checked against the bundled factory Data List before it is printed. Deep specialisation in Hindi / Bollywood (sargam sources, raag feel, Indian-instrument substitutions) but works for any song. Use whenever the user says "play [song]", "notes for [song]", "chords for [song]", "scale of [song]", "song sheet", "make a sheet", or asks about their PSR-SX — whether a voice exists or must be substituted, styles, accompaniment, split point, Registration Memory, Multi Pads, mic, transpose, effects.
HelloIamChetan/sargam-psr-sx · ★ 0 · AI & Automation · score 63

Install: claude install-skill HelloIamChetan/sargam-psr-sx

# SARGAM — PSR-SX song sheets Turn a song into a **printable PDF the user can play from**: scale, chords, panel setup, and full notation. The sheet lives on a music stand, so it is built to be read at arm's length with both hands busy. Two things separate a good sheet from a plausible one, and both are mechanical rather than a matter of care: - **Preset names are checked, not recalled.** `scripts/presets.py` holds Yamaha's published factory list. A name is in it or it is not. Never print one you have not checked — see `references/inventory.md`. - **The sheet says what it does not know.** Coverage is scored out of 10 and printed on the sheet. An honest gap is useful; an invented interlude is worse than a blank one. ## Step 0 — config and model Look for `psr-sx.config.md` (or any `*psr*config*.md` / `*keyboard*config*.md`) in the working folder or a connected folder, or attached to the conversation. It carries the user's model, their expansion packs, their Registration Memory slots and their preferences. `assets/config.md` is the blank; `references/models.md` covers what differs between SX600, SX700 and SX900. No config? Work from the model the user names, or ask once which model they have — it changes the preset list, the knob count and whether Vocal Harmony exists. Then offer to write a config so they never have to say it again. ## The loop | The user says | Do | |---|---| | "play X", "set up X", "notes for X", "make a sheet for X" | Full sheet: research → build → PDF