mc-case-studies

Validates music arrangement rules against a corpus of 63 reverse-engineered ARR-SPEC entries.

128|16|Updated Sep 17, 2026
One-click install
npx skills add https://github.com/jtydhr88/music-composition-skills --skill mc-case-studies-jtydhr88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mc-case-studies
Source: https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-case-studies
Command: npx skills add https://github.com/jtydhr88/music-composition-skills --skill mc-case-studies-jtydhr88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Textbook music arrangement rules are often repeated without evidence. This Skill answers whether real recordings actually follow those rules by cross-checking each rule against a corpus of 63 measured ARR-SPEC entries derived from Cambridge-MT multitracks, producing hit rates and tiered evidence levels (strong rule / tendency / technique / suspended). ## Core Features & Use Cases - Corroboration Table: Maps rules against the corpus to compute hit rates and assign evidence tiers, with two honesty constraints preventing circular validation. - Reverse ARR-SPEC Corpus: Uses structure-and-parameter-only entries (no audio, scores, or lyrics) with honest TODO markers for fields machines cannot measure. - Conflict Resolution: Provides a procedure for when rules and data disagree—suspect the criterion before the rule, illustrated by real cases like the hardcoded 12 dB threshold that produced a false 16% hit rate. - Use Case: When adding a new arrangement rule to the library, run it through the corroboration workflow to check whether it qualifies as a strong rule eligible for the 20-item self-check lint table. ## Quick Start Ask the agent to check whether a specific arrangement rule holds in real music and what evidence tier it belongs to.

Frequently Asked Questions about mc-case-studies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify whether a music arrangement rule holds in real recordings?▼

Check the corroboration table, which cross-references each rule against 63 measured ARR-SPEC entries from Cambridge-MT multitracks and reports a hit rate. Rules are tiered as strong rule, tendency, technique, or suspended based on the results.

What is a reverse ARR-SPEC in music analysis?▼

A reverse ARR-SPEC is a corpus entry reverse-engineered from audio that stores only measured structure and parameters—sections, roster entry/exit, energy curve—without audio, scores, or lyrics. Fields machines cannot measure, like intent, are left as honest TODO markers.

What can the Cambridge-MT multitrack corpus measure and not measure?▼

It can measure section boundaries, tempo, energy curves, instrumentation entry/exit, and chords. It cannot measure dynamic range, loudness, stereo width, or absolute spectral centroid because the tracks are unmixed multitracks, and such rules are marked unusable_here rather than run.

Why does a low hit rate not automatically disprove a music rule?▼

A low hit rate often means the criterion measures the wrong thing, not that the rule is false. One rule showed 22% on the full corpus but 5/7 on human-annotated ground truth because the algorithm located climaxes by energy peak while human ears do not.

Which rules qualify for the 20-item arrangement self-check lint?▼

Only strong rules—those with very high corpus hit rates like 62/62—enter the lint as hard checks. Tendencies go into a post-writing checklist, techniques appear only in diagnostic paths, and suspended rules stay out of the skill entirely.