Skip to content
Skills Library
Other · Building & coding

score

/score

Turn a musical brief into editable concert-pitch music, checked instrument parts and a listenable practice pack in the Score harness. Use for composing, arranging and revising trusted LilyPond projects.

Repository
openharness ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
11
Scripts
7
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 7 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/archive.mjs, scripts/build.mjs, scripts/ensemble.mjs, scripts/lilypond.mjs, scripts/midi.mjs, scripts/preview.js, scripts/render-score.sh

What it does and when to use it

Turn a musical brief into editable concert-pitch music, checked instrument parts and a listenable practice pack in the Score harness. Use for composing, arranging and revising trusted LilyPond projects.

Original author description

Turn a musical brief into editable concert-pitch music, checked instrument parts and a listenable practice pack in the Score harness. Use for composing, arranging and revising trusted LilyPond projects.

How it works

  1. Compose and revise
  2. Hear and hand off
  3. Boundaries
Original SKILL.md headings · 79 lines, 597 words
SKILL.md preview
---
name: score
description: Turn a musical brief into editable concert-pitch music, checked instrument parts and a listenable practice pack in the Score harness. Use for composing, arranging and revising trusted LilyPond projects.
---

# From a musical idea to something the user can keep

The user does not need instruments or notation vocabulary. If they want to
listen, start with mood, purpose, duration and a useful instrumentation; state
assumptions and offer an audible first version. If they have real players,
capture each player's instrument, written range and experience. Do not turn the
starter trio or any particular difficulty limit into a universal requirement.

Read [the ensemble contract](references/ensemble.md) before changing player
setup, timing, difficulty or source exports.

## Compose and revise

- Save the actual brief, assumptions, timing, instrument transpositions and
  difficulty limits in `ensemble.json`. These are requirements, not values to
  infer from whatever the generated notes happen to contain.
- Compose reusable **concert-pitch** variables in `score.ly`; the builder adds
  the initial key, meter, tempo, printed score, parts and MIDI proofs. Do not
  transpose the source again for a B-flat part or override staff transposition.
- Give the music a deliberate shape: phrases, breathing space, contrast,
  accompaniment and an ending appropriate to the request. A successful compiler
  does not supply those decisions.
- Run:

  ```sh
  sh "$SCORE_SKILLS/score/scripts/render-score.sh"
  ```

- Inspect `.harness/score.json` and every printed PDF page, including individual
  parts. Check collisions, readability, instrument labels and sensible breaks.
  LilyPond warnings are errors. Correct the music or layout, not the warning policy.
- On a failed requirement, read `.harness/failed-score.json`. Fix the music while
  retaining the user's limits. Change a requirement only when the request
  genuinely changes; explain a conflict instead of quietly widening a range.
- For a targeted revision, verify the requested change and compare unaffected
  parts. Keep a useful previous version; generated handoffs are retained under
  `.harness/history/`.

## Hear and hand off

Use `score.html` in the actual viewer. Exercise play/pause, seeking into a held
note, player mute/solo, slowdown, bar loops and part selection. No instrument
is needed. The browser can save a WAV of the current mix/loop (up to 3 minutes).
Save/restore listening setup as JSON; no local storage is required.

The source-backed delivery is `score-project.zip`: full PDF/MIDI, individual
parts, slower solo/minus-one MIDI, the saved brief, allowlisted sources and
standalone rebuild tools. Test important downloads. Browser controls and WAV
exports do not change `score.ly` or the prebuilt practice MIDIs. To change the
composition, edit the sources and rebuild.

Report the version, checks and listening/visual review actually performed.
Offer concrete revisions in the user's language (“make the ending warmer,”
“remove the busy line”), not a requirement to learn notation first.

## Boundaries

Setup installs LilyPond 2.26.0 when needed on supported Macs/Linux x86-64; the builder
finds that managed runtime automatically. Node 20+ comes from the runtime helper.
`LILYPOND_BIN` overrides the binary. Only compile trusted input: LilyPond can execute Scheme and read local
files. The source allowlist makes delivery explicit; it is not a Scheme sandbox.
Do not add unrelated files, credentials or recordings to the portable project.

Ready means fresh engraving and the saved **mechanical** requirements passed,
not proof of musical quality, comfort, breath control, fingering, physical
playability or permission to use an arrangement. A synthesized sketch is not
a recording or sampled performance. No real-player testing is implied.

This checked workflow supports constant meter/tempo, complete bars and pitched
staves. See the contract for limits and excluded cases. Original native MIDI
is retained; practice exports and browser audio ignore pedal, bends and other
expressive controllers. The browser uses simple oscillators, not a sound library.

Legacy `score.ly` projects containing full layout/MIDI blocks still engrave
without an ensemble contract, but remain unready for checked delivery. Preserve
their source and extract music variables deliberately when upgrading. Do not
blindly replace a user's composition with the template.
Files in this package (11)
  • SKILL.md 4 KB
  • references/ensemble.md 5 KB
  • scripts/LICENSE 1 KB
  • scripts/archive.mjs 2 KB
  • scripts/build.mjs 15 KB
  • scripts/ensemble.mjs 14 KB
  • scripts/lilypond.mjs 6 KB
  • scripts/midi.mjs 8 KB
  • scripts/preview.html 10 KB
  • scripts/preview.js 16 KB
  • scripts/render-score.sh 1 KB

Versions

RepositoryScoreLicence
This page · autonomous-ai/openharness100MIT
andryorelabs/jobship100MIT
sejas/ai-code-skills100MIT
Esposter/Esposter90Apache-2.0
clockgrove/factory90MIT
gagoar/iceberg87MIT
Hainrixz/claude-seo-ai86MIT
hainrixz/claude-db86MIT

Database snapshot: 13.11.2026 · package version b830db660860 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90music-composition
    Use when composing, developing or revising musical ideas in a DAW. Focus on meaningful musical development rather than merely repeating patterns or adding layers.
  • 100sheet-music-pdf-convert
    Turn a sheet music PDF (exported from notation software, scanned, or photographed) into editable MusicXML that opens in MuseScore, Dorico, Sibelius or Finale. Use when the user wants to edit, transpose, re-engrave or play back a score they only have as a PDF, asks to "convert…
  • 100musical-instrument-repairer-tuner
    Use when a task needs the judgment of a Musical Instrument Repairer and Tuner — aurally tuning a piano to a stretched temperament, regulating a grand or upright action, reseating and leak-testing woodwind pads, aligning brass valves and slides, setting up a guitar or violin's…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.