Skip to content
Back to search

music-composition

Modular music-composition skill for AI assistants — harmony, melody, form, 24+ genres.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sjy051--music-composition/badge.svg)](/listings/sjy051--music-composition)

HTML

<a href="/listings/sjy051--music-composition"><img src="/api/listings/sjy051--music-composition/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The simplest way is via the [`skills` CLI](https://www.npmjs.com/package/skills) (requires Node.js):

npx skills add SJY051/music-composition

This installs to your current project's agent directory (e.g., `.claude/skills/`). Add `-g` for user-level (global) install, or `--all -y` to skip prompts.

For a manual install, clone the repository and point your agent at it (or copy `SKILL.md` and the relevant subdirectories into your agent's skill folder, such as `~/.claude/skills/` or `.claude/skills/` in a project):

git clone https://github.com/SJY051/music-composition.git

Compatibility

The skill follows the open **Agent Skills standard** — the SKILL.md + YAML frontmatter format used by both [Claude](https://code.claude.com/docs/en/skills.md) (Claude Code, Claude Agent SDK, Claude.ai skills) and [OpenAI](https://developers.openai.com/api/docs/guides/tools-skills) (Responses API `tools[].environment.skills`). It works on any harness that reads this format.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 156 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: music-composition
  3. description: Use this skill whenever the user asks for help with music composition, music theory, songwriting, harmony, melody, counterpoint, arrangement, orchestration, or musical analysis — across classical, jazz, pop, rock, hip-hop, R&B, electronic, film/TV, K-pop/J-pop, folk, or musical theatre. Triggers include explicit theory questions ("what scale fits over Cm7", "explain ii-V-I", "modulate from C to E♭"), craft questions ("write a chord progression for a melancholy bridge", "make this melody more memorable", "voice this chord on piano"), and vague creative problems that map to compositional techniques ("the chorus feels weak", "this transition is awkward", "my song sounds generic"). Use this skill even when the user describes the goal in non-technical terms — translating fuzzy creative problems into concrete compositional moves is exactly what this skill is for. Do NOT use for DAW operation, MIDI file generation, audio engineering, mixing/mastering, sound design, or notation software UI.
  4. ---
  5. # Music Composition
  6. A comprehensive composition skill covering music theory and compositional craft for both DAW-based and acoustic/score-based workflows. This skill does NOT handle DAW automation, MIDI generation, audio engineering, or notation software — those belong to other skills.
  7. ## Core philosophy
  8. Composition is a series of decisions, not a list of rules to follow. When advising:
  9. - **Frame techniques as options, not commandments.** A "rule" in voice-leading is a probability distribution that creates a certain sound. Breaking it makes a different sound, which may be exactly what's wanted. Always know which sound the user is after.
  10. - **Explain *why* a technique produces its effect.** Cite the perceptual or contextual reason — "the leading tone resolves up because the half-step gravity is strong and the ear expects closure". This lets the user reason about novel situations rather than memorize rules.
  11. - **When the user describes a feeling or goal, give multiple options.** "I want this to feel uneasy" has many valid solutions (tritone substitution, modal mixture, polychords, rhythmic displacement). Offer 2–4 with their trade-offs rather than picking one.
  12. - **Be concrete.** "Try a iv chord" beats "try modal mixture." "Voice this with the 3rd on top in close position, low E in the bass" beats "make it tighter." Always give the user something they can play.
  13. - **Respect genre conventions but don't be enslaved by them.** A "wrong" choice in jazz might be perfect in indie rock. Always know which genre frame the user is operating in.
  14. - **When the user describes a vague creative problem, translate it before answering.** "The chorus feels weak" decomposes into: melodic range, harmonic surprise, dynamic contrast, arrangement density, rhythmic activity, lyric/syllable density. Diagnose, then prescribe.
  15. - **Don't moralize about technique.** Parallel fifths aren't immoral. They're a sound. Bach avoided them; Debussy used them; the user's track might want them.
  16. ## What this skill does NOT cover
  17. - **DAW operation** — keyboard shortcuts, plugin parameters, automation lanes (separate skill).
  18. - **MIDI file generation or direct manipulation** — handled elsewhere.
  19. - **Audio engineering / mixing / mastering / sound design** — frequency-aware *composition* is in `production-aware/`, but EQ, compression, and synthesis decisions are out of scope.
  20. - **Music history trivia** unconnected to composition technique. (Stylistic conventions of a period ARE in scope.)
  21. - **Music notation software operation** (Sibelius, Finale, Dorico, MuseScore UI).
  22. - **Performance pedagogy or instrumental exercise routines** for becoming a player. Composition-facing playability and idiomatic writing are in `references/instrument-idiom/`, but this skill does not replace a private teacher, method book, or technique practice plan.
  23. ## Navigation
  24. The bulk of this skill lives in `references/`. **Always start by reading `references/00-navigation.md`** — it maps user requests to the specific reference files you need.
  25. Don't load every reference. Load only what's directly relevant to the current question. For most requests, 1–3 reference files is enough. If you would need 5+, the question is too broad — narrow it first, or pick the dominant aspect and answer that.
  26. For quick lookups (chord progression catalogs, mode formulas, voicing libraries), check `assets/`. Asset files are short and can be quoted directly. Reference files should be synthesized, not quoted.
  27. ## Top-level structure
  28. ```
  29. references/
  30. ├── 00-navigation.md ← Read this first, every time
  31. ├── fundamentals/ ← Pitch, intervals, scales, rhythm, notation, prosody
  32. ├── harmony/ ← Chords, voice leading, modulation, jazz, modal, reharm
  33. ├── melody/ ← Construction, motivic development, phrase structure
  34. ├── counterpoint.md ← Species → tonal → fugue
  35. ├── rhythm-groove/ ← Rhythmic devices, groove/feel, odd meters
  36. ├── form/ ← Classical & popular forms, narrative
  37. ├── orchestration/ ← Instruments, voicing, texture, density, choral writing
  38. ├── instrument-idiom/ ← Composition-facing playability for piano, guitar, bass, drums, strings, winds, brass, vocals
  39. ├── genres/ ← Per-genre conventions (incl. Korean traditional, C-pop / SE Asian, Latin, Afrobeats, MENA, South Asian, country, metal, gospel, Brazilian, game, media/commercial)
  40. ├── songwriting/ ← Lyrics, hooks, topline
  41. ├── analysis.md ← Roman numeral, form, Schenker, set theory
  42. ├── techniques/ ← Theme & variation, 20th C., constraint-based, microtonal, algorithmic / AI-assisted
  43. ├── production-aware/ ← Pre-production, composition-mix interface, energy
  44. ├── research/ ← Web trends, user listening context, regional trend evolution, reference digging, style/copyright guardrails
  45. ├── creative-workflows/ ← Musical brainstorming, answer calibration, revision loops, and user-agent collaboration patterns
  46. ├── validation/ ← Release readiness, Phase B/C records, RC packaging, and prompt smoke tests
  47. ├── source-bibliography.md ← Maintainer-facing source map and verification guide
  48. ├── workflow.md ← Starting, revising, hybrid-genre advising
  49. ├── critique-and-feedback.md ← Evaluating user's existing work (critique mode)
  50. └── teaching-composition.md ← Pedagogy mode, learning paths, exercises
  51. scripts/
  52. └── music_theory_sanity_check.py ← Optional validation and regression helper for maintainers
  53. assets/
  54. ├── progressions-catalog.md
  55. ├── response-templates.md
  56. ├── diagnostic-checklists.md
  57. ├── trend-and-reference-matrices.md
  58. ├── musical-brainstorming-cards.md
  59. ├── session-brief-and-decision-log.md
  60. ├── web-search-cheatsheet.md
  61. ├── chord-symbol-ambiguity-and-parsing.md
  62. ├── scale-degree-spelling-cheatsheet.md
  63. ├── music-theory-audit-rubric.md
  64. ├── cadence-reference.md
  65. ├── modes-cheatsheet.md
  66. ├── intervals-and-scale-formulas.md
  67. ├── jazz-voicings.md
  68. ├── form-templates.md
  69. └── chord-symbol-conventions.md
  70. ```
  71. ## Typical response workflow
  72. 1. **Identify the user's actual ask.** Surface goal (e.g., "write a sad chord progression in C") and underlying goal (e.g., "I want emotional weight without sounding cliché"). They're often different.
  73. 2. **Identify the genre frame.** A "sad chord progression" means very different things in chamber music, neo-soul, lo-fi hip-hop, and K-pop ballad. If unstated and ambiguous, ask. If implied, work with it but name the assumption.
  74. 3. **Read `references/00-navigation.md`** to find the relevant reference files.
  75. 4. **Load the minimal set** of reference files needed.
  76. 5. **Translate theory into concrete options.** Don't dump theory — produce 2–4 actionable suggestions with brief rationale and a clear sample (chord names, notes, rhythm).
  77. 6. **Note adjacent considerations** the user may not have thought of (e.g., "this works in C, but if you modulate to the relative minor at the bridge, you open up `iv–i–V–i`, which is darker still").
  78. 7. **Stop before over-explaining.** A concise, useful answer beats a comprehensive lecture.
  79. ## Notation conventions
  80. Use these consistently throughout the skill:
  81. - **Chord symbols** (lead-sheet / jazz style): `Cmaj7`, `Dm7`, `G7♭9`, `F♯dim7`, `B♭/D` (slash chord), `Cmaj7♯11`.
  82. - **Roman numerals**: capital = major triad, lowercase = minor; `°` = diminished, `+` = augmented; arabic for inversions and 7ths (`I`, `vi`, `V7`, `ii⁶`, `V⁶/⁵`, `vii°⁷`, `iiø7`); `♭` and `♯` prefix for chromatic alterations of scale degree (`♭VI`, `♯iv°`); `/` for tonicization (`V/V`, `V7/vi`).
  83. - **Pitches**: scientific pitch notation when register matters (C4 = middle C); plain letter names when unambiguous. Sharp = `♯`, flat = `♭`, double-sharp = `𝄪`, double-flat = `𝄫`.
  84. - **Intervals**: `m2 M2 m3 M3 P4 A4 d5 P5 m6 M6 m7 M7 P8`; "tritone" acceptable when style is informal.
  85. - **Scale degrees**: `^1 ^2 ^3 ...` when concise; "tonic / supertonic / mediant / subdominant / dominant / submediant / leading tone" in prose.
  86. - **Tempo**: BPM (`120 BPM`); `♩=120` when discussing notation.
  87. ## Genre framing — always required
  88. The same musical question has different answers in different genres. Before applying any technique, identify the genre frame:
  89. - Classical (which period?)
  90. - Jazz (which sub-style?)
  91. - Pop / rock / indie
  92. - Hip-hop / R&B / neo-soul
  93. - Electronic (which sub-style?)
  94. - Film / TV (what dramatic context?)
  95. - Game / interactive media (what platform / interactive system?)
  96. - Advertising / podcast / branded content / trailer / library music
  97. - K-pop / J-pop
  98. - C-pop / Cantopop / T-pop / V-pop / OPM / Indo-pop
  99. - Latin pop / reggaeton / urbano
  100. - Brazilian pop / MPB / samba-pop / funk carioca
  101. - Afrobeats / amapiano
  102. - South Asian film-pop / raga-derived pop
  103. - MENA pop / maqam-adjacent fusion
  104. - Korean traditional (*gugak*) and K-trad fusion
  105. - Country / Americana / roots
  106. - Metal / punk / hardcore
  107. - Gospel / CCM / worship
  108. - Folk / roots / tradition-specific writing
  109. - Regional scene starters and local-pop idioms
  110. - Minor / microgenre / hybrid scenes
  111. - Musical theatre
  112. If the user hasn't named one and context doesn't make it obvious, ask. Don't default silently — you'll give wrong-feeling advice.
  113. ## Extensibility
  114. This skill is designed to grow. To add new content:
  115. 1. **New genre or sub-genre**: add `references/genres/<name>.md`, update `00-navigation.md`'s genre table.
  116. 2. **New technique**: add to the most relevant existing folder, or create a new sub-folder if the topic is large enough to warrant 3+ files.
  117. 3. **New cheatsheet / matrix asset**: add to `assets/`, update `00-navigation.md`'s asset map.
  118. 4. **New instrument idiom**: add `references/instrument-idiom/<instrument>.md`, update `instrument-idiom/overview.md` and `00-navigation.md`.
  119. 5. **New current-research workflow**: add to `references/research/`, include a snapshot note, update `00-navigation.md`, and link from related genre files.
  120. 6. **New user-agent creative workflow**: add to `references/creative-workflows/`, update `00-navigation.md`, and add quick templates in `assets/` if the workflow benefits from reusable cards. Use `creative-workflows/answer-calibration.md` for bounded variation, answer length, and loading discipline.
  121. 7. **New validation / release-readiness file**: add to `references/validation/`, update `00-navigation.md`, `RELEASE-ROADMAP.md` if relevant, and add expected-file checks when it becomes release-critical. Ship `KNOWN-LIMITATIONS.md` or include its caveats in release validation reports.
  122. When adding files, keep them under ~600 lines (split if longer), one topic per file, descriptive names. Always update `00-navigation.md` so the agent can find new content.
  123. Recent expansion includes game/interactive scoring, microtonal/xenharmonic systems, choral writing, music for media, Korean traditional / K-trad fusion, C-pop / Southeast Asian pop, prosody, and algorithmic / AI-assisted composition. Recent expansion also includes response templates, diagnostic checklists, trend/reference matrices, musical brainstorming cards, session/decision-log templates, a web-search cheatsheet, style/copyright guardrails, user streaming-service listening context, regional trend-evolution analysis, regional scene starters, minor/microgenre handling, genre idiom files for Latin pop/reggaeton, Afrobeats/amapiano, South Asian film-pop, MENA pop, country/Americana, metal/punk/hardcore, gospel/CCM, and Brazilian pop/funk, plus composition-facing `instrument-idiom/`, `creative-workflows/`, and `validation/` folders, release-readiness docs, Phase C smoke-test result recording, RC1 packaging guidance, known-limitations documentation, answer-calibration workflow guidance, chord-symbol/scale-degree audit assets, and a maintainer-facing source bibliography. Future additions should prioritize prompt-smoke-test runs, deeper regional genre idioms, instrument-family expansions where needed, style-specific reference libraries, and stronger automated validation; the Phase B correctness-prep checklist now lives in `references/validation/phase-b-correctness-pass.md`.
  124. ## Honesty about gaps
  125. If a user asks about a topic this skill doesn't yet cover, say so explicitly: "This skill doesn't have a dedicated reference for [X] yet — I'll work from general principles and flag what I'm uncertain about." Then do that. Don't fabricate confident answers from gaps.
README.md · README · 337 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. [English](./README.md) | [한국어](./README.ko.md)
  2. # Music Composition Agent Skill
  3. ![Version](https://img.shields.io/badge/version-1.0-blue) ![Docs License](https://img.shields.io/badge/docs-CC%20BY%204.0-green) ![Code License](https://img.shields.io/badge/code-MIT-blue) ![Compatibility](https://img.shields.io/badge/compatibility-any%20SKILL.md%20harness-orange)
  4. A modular knowledge and workflow skill for an AI music-composition assistant.
  5. This repository is designed to help an agent turn vague creative requests — “make the chorus hit harder,” “give me a darker K-pop bridge,” “reharmonize this like jazz but not too dense,” “find reference tracks for my playlist” — into concrete musical decisions: chords, melody shapes, grooves, forms, arrangement moves, diagnostic feedback, and research workflows.
  6. **Current release:** `v1.0`
  7. **Release date:** `2026-04-27`
  8. ---
  9. ## Installation
  10. The simplest way is via the [`skills` CLI](https://www.npmjs.com/package/skills) (requires Node.js):
  11. ```bash
  12. npx skills add SJY051/music-composition
  13. ```
  14. This installs to your current project's agent directory (e.g., `.claude/skills/`). Add `-g` for user-level (global) install, or `--all -y` to skip prompts.
  15. For a manual install, clone the repository and point your agent at it (or copy `SKILL.md` and the relevant subdirectories into your agent's skill folder, such as `~/.claude/skills/` or `.claude/skills/` in a project):
  16. ```bash
  17. git clone https://github.com/SJY051/music-composition.git
  18. ```
  19. ### Compatibility
  20. The skill follows the open **Agent Skills standard** — the SKILL.md + YAML frontmatter format used by both [Claude](https://code.claude.com/docs/en/skills.md) (Claude Code, Claude Agent SDK, Claude.ai skills) and [OpenAI](https://developers.openai.com/api/docs/guides/tools-skills) (Responses API `tools[].environment.skills`). It works on any harness that reads this format.
  21. ---
  22. ## Does it work?
  23. Two benchmarks ship with v1.0:
  24. **Approach 1 (system-prompt injection, GLM-5.1, blind eval).** With `SKILL.md` prepended to the system prompt, the skill version wins **6 of 8** representative composition prompts in an author-bias-controlled blind comparison. The strongest signal is the boundary test (P8) — the skill version explicitly declines an out-of-scope mixing question while the baseline answers freely.
  25. ![GLM-5.1 blind evaluation — wins per condition](./benchmarks/charts/chart_glm_winners.png)
  26. **Approach 2 (native lazy loading, Claude Opus 4.7).** With the skill installed via Claude Desktop's Skills feature, the model reads references on demand. Most striking: pansori OST advice cites *yoseong*, *toeseong*, *chuseong* with cents-and-milliseconds implementation values that exist only inside `references/genres/korean-traditional.md` — direct evidence the model used the skill's full content, not just `SKILL.md`.
  27. ![P8 boundary respect across both benchmarks](./benchmarks/charts/chart_p8_boundary.png)
  28. Together: **the skill content shapes behavior even on weaker setups, and content depth unlocks on stronger setups.** Full methodology and per-prompt analysis: [`benchmarks/v1.0-eval.md`](./benchmarks/v1.0-eval.md), [`benchmarks/v1.0-claude.md`](./benchmarks/v1.0-claude.md).
  29. ---
  30. ## What this skill is for
  31. Use this skill when an AI agent needs to help with:
  32. - composition brainstorming
  33. - chord progressions and harmonic direction
  34. - melody, motif, phrase, and topline writing
  35. - song forms, transitions, and narrative structure
  36. - rhythm, groove, meter, and feel
  37. - orchestration, arrangement, voicing, and instrument idiom
  38. - genre-aware writing across pop, jazz, classical, game, media, regional, traditional, and hybrid styles
  39. - critique and revision of a work in progress
  40. - teaching music concepts in a practical composition-first way
  41. - current music trend research and reference-track digging
  42. - user-agent collaborative workflows across multiple turns
  43. The skill is not a DAW, audio engine, MIDI generator, transcription engine, legal service, or substitute for a human specialist in culturally specific traditions. It is a structured reference and workflow layer for an AI assistant.
  44. ---
  45. ## Core design philosophy
  46. The skill is built around a few practical principles:
  47. 1. **Composition is decision-making, not rule-following.**
  48. Music theory is treated as a map of possible effects, not a list of commandments.
  49. 2. **Give playable, actionable output.**
  50. Prefer concrete examples such as chord charts, scale-degree melodies, groove sketches, voicing suggestions, and revision blocks.
  51. 3. **Preserve user agency.**
  52. Offer options, explain tradeoffs, and let the user choose a direction.
  53. 4. **Use only the references needed.**
  54. The agent should usually start with `SKILL.md`, route through `references/00-navigation.md`, and load only the most relevant 1–3 files.
  55. 5. **Treat current music trends as research tasks.**
  56. Static genre files provide stable craft conventions. Recent artists, charts, platform norms, and scene-specific references should be checked through active web research.
  57. 6. **Avoid shallow cultural shortcuts.**
  58. Tradition-specific and region-specific music should not be reduced to generic “flavor.” The skill encourages naming the source tradition, function, language, rhythm system, instrumentation, and collaboration needs.
  59. ---
  60. ## Repository structure
  61. ```text
  62. .
  63. ├── SKILL.md
  64. ├── MAINTENANCE.md
  65. ├── RELEASE-ROADMAP.md
  66. ├── KNOWN-LIMITATIONS.md
  67. ├── RELEASE-NOTES-v1.0.md
  68. ├── VALIDATION-v1.0.md
  69. ├── assets/
  70. ├── references/
  71. │ ├── 00-navigation.md
  72. │ ├── creative-workflows/
  73. │ ├── form/
  74. │ ├── fundamentals/
  75. │ ├── genres/
  76. │ ├── harmony/
  77. │ ├── instrument-idiom/
  78. │ ├── melody/
  79. │ ├── orchestration/
  80. │ ├── production-aware/
  81. │ ├── research/
  82. │ ├── rhythm-groove/
  83. │ ├── songwriting/
  84. │ ├── techniques/
  85. │ └── validation/
  86. └── scripts/
  87. └── music_theory_sanity_check.py
  88. ```
  89. ### Important files
  90. | File | Purpose |
  91. |---|---|
  92. | `SKILL.md` | Root operating instructions for the agent. Start here. |
  93. | `references/00-navigation.md` | Routing map for choosing the right reference files. |
  94. | `assets/` | Short cheat sheets and response templates for quick use. |
  95. | `references/creative-workflows/` | Brainstorming, revision, answer calibration, and user-agent collaboration. |
  96. | `references/research/` | Web trend research, reference-track digging, streaming-service-aware research, and style/copyright guardrails. |
  97. | `references/genres/` | Genre and regional starter guides. |
  98. | `references/instrument-idiom/` | Composition-facing playability and idiomatic writing guides. |
  99. | `references/validation/` | Release readiness, smoke tests, correctness passes, and packaging checklists. |
  100. | `scripts/music_theory_sanity_check.py` | Regression checker for links, known theory errors, risky terminology, snapshot notes, and required files. |
  101. ---
  102. ## Suggested agent workflow
  103. For most user requests:
  104. ```text
  105. 1. Read SKILL.md.
  106. 2. Use references/00-navigation.md to identify the smallest useful document set.
  107. 3. Load only the relevant reference files, usually 1–3.
  108. 4. Generate concrete musical output.
  109. 5. Explain why the choices work.
  110. 6. Offer a small number of next-step options.
  111. ```
  112. For example:
  113. | User request | Likely routing |
  114. |---|---|
  115. | “Give me a sad but not cliché progression.” | `harmony/functional-harmony.md`, `harmony/modal-harmony.md`, `assets/progressions-catalog.md` |
  116. | “The chorus does not hit.” | `assets/diagnostic-checklists.md`, `songwriting/hooks-and-memorability.md`, `production-aware/energy-and-dynamics.md` |
  117. | “Make this more playable on guitar.” | `instrument-idiom/guitar.md`, plus the relevant harmony or arrangement file |
  118. | “Brainstorm three directions.” | `creative-workflows/musical-brainstorming.md`, `assets/musical-brainstorming-cards.md` |
  119. | “Find current J-pop references.” | `research/web-music-trend-research.md`, `research/reference-track-digging.md`, `assets/web-search-cheatsheet.md` |
  120. | “Use my playlist as a reference.” | `research/user-listening-context-and-streaming-services.md`, `assets/trend-and-reference-matrices.md` |
  121. ---
  122. ## Currentness policy
  123. Some files include a snapshot note. These files contain information that can become outdated, especially around:
  124. - current genre trends
  125. - charts and streaming-platform behavior
  126. - artist references
  127. - regional scenes
  128. - AI-assisted music tools
  129. - copyright and policy developments
  130. The snapshot note does not mean the file is permanently current. It means the file was last reviewed as of that snapshot date. For fresh claims, use the research documents and verify current sources.
  131. Useful research files:
  132. ```text
  133. references/research/web-music-trend-research.md
  134. references/research/reference-track-digging.md
  135. references/research/user-listening-context-and-streaming-services.md
  136. references/research/regional-trend-evolution-analysis.md
  137. references/research/style-reference-and-copyright.md
  138. assets/web-search-cheatsheet.md
  139. ```
  140. ---
  141. ## Style, originality, and copyright guardrails
  142. This skill is intended to help generate original musical ideas. It should not be used to copy protected expression from existing songs or artists.
  143. When a user asks for a specific artist or song style, the agent should translate the reference into craft variables such as:
  144. - tempo range
  145. - groove type
  146. - harmonic density
  147. - form
  148. - vocal range and phrasing style
  149. - arrangement density
  150. - instrumentation
  151. - energy curve
  152. - production-era cues
  153. The agent should avoid reproducing or imitating protected elements such as:
  154. - melody
  155. - lyrics
  156. - distinctive riffs
  157. - samples
  158. - signature producer tags
  159. - highly specific vocal identity
  160. - recognizable arrangement sequences from a particular recording
  161. See:
  162. ```text
  163. references/research/style-reference-and-copyright.md
  164. KNOWN-LIMITATIONS.md
  165. ```
  166. ---
  167. ## Cultural and regional specificity
  168. The skill contains guides for traditional, regional, and hybrid styles. These are composition-facing starter references, not replacements for cultural expertise, native-language knowledge, or practitioner collaboration.
  169. When working with culturally specific material, prefer:
  170. ```text
  171. specific tradition / region / language / function / rhythm / instrument idiom / performance context
  172. ```
  173. Instead of vague labels such as:
  174. ```text
  175. generic world flavor / ethnic color / Asian flavor / Middle Eastern flavor
  176. ```
  177. Relevant files include:
  178. ```text
  179. references/genres/korean-traditional.md
  180. references/genres/folk-roots-and-traditions.md
  181. references/genres/mena-pop.md
  182. references/genres/south-asian-film-pop.md
  183. references/genres/regional-scene-starters.md
  184. references/research/regional-trend-evolution-analysis.md
  185. ```
  186. ---
  187. ## Validation
  188. The v1.0 package passed the release validation recorded in:
  189. ```text
  190. VALIDATION-v1.0.md
  191. references/validation/first-release-readiness.md
  192. references/validation/phase-b-correctness-pass.md
  193. references/validation/phase-c-smoke-test-results.md
  194. ```
  195. To run the sanity checker:
  196. ```bash
  197. python scripts/music_theory_sanity_check.py
  198. ```
  199. The checker looks for issues such as:
  200. - broken internal Markdown references
  201. - known high-risk music-theory regressions
  202. - risky cultural shortcut terminology
  203. - missing snapshot notes in current-sensitive files
  204. - required release and validation files
  205. - selected interval, mode, chord-symbol, and altered-dominant sanity checks
  206. This checker is a regression tool, not a complete proof of musical correctness.
  207. ---
  208. ## Maintenance
  209. Before changing the repository:
  210. 1. Read `MAINTENANCE.md`.
  211. 2. Update `references/00-navigation.md` when adding or moving files.
  212. 3. Keep high-use assets concise and accurate.
  213. 4. Use snapshot notes for current-sensitive files.
  214. 5. Run `scripts/music_theory_sanity_check.py`.
  215. 6. Record substantial validation work in the relevant validation document.
  216. Recommended versioning:
  217. | Change type | Suggested version |
  218. |---|---|
  219. | Typo, link, or small validation-script fix | `v1.0.x` |
  220. | P0/P1 correctness hotfix | `v1.0.x` hotfix |
  221. | New genre, workflow, or research documents | `v1.1` |
  222. | Larger parser/evaluation harness improvements | `v1.1` or `v1.2` |
  223. | Major structure change or file reorganization | `v2.0` candidate |
  224. ---
  225. ## Known limitations
  226. See `KNOWN-LIMITATIONS.md` for the full list.
  227. In brief, this skill does not directly provide:
  228. - audio transcription
  229. - DAW control
  230. - MIDI export
  231. - audio mixing or mastering
  232. - legal advice
  233. - guaranteed current trend knowledge without web research
  234. - exhaustive expertise in every local or traditional music practice
  235. ---
  236. ## License
  237. This repository uses a split license:
  238. - Skill documents, references, assets, release notes, and validation documents are licensed under **Creative Commons Attribution 4.0 International (CC BY 4.0)**.
  239. - Code in `scripts/` is licensed under the **MIT License**.
  240. See `LICENSE.md` for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.