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.
Badge for your README
Markdown
[](/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
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)
- ---
- name: music-composition
- 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.
- ---
- # Music Composition
- 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.
- ## Core philosophy
- Composition is a series of decisions, not a list of rules to follow. When advising:
- - **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.
- - **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.
- - **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.
- - **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.
- - **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.
- - **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.
- - **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.
- ## What this skill does NOT cover
- - **DAW operation** — keyboard shortcuts, plugin parameters, automation lanes (separate skill).
- - **MIDI file generation or direct manipulation** — handled elsewhere.
- - **Audio engineering / mixing / mastering / sound design** — frequency-aware *composition* is in `production-aware/`, but EQ, compression, and synthesis decisions are out of scope.
- - **Music history trivia** unconnected to composition technique. (Stylistic conventions of a period ARE in scope.)
- - **Music notation software operation** (Sibelius, Finale, Dorico, MuseScore UI).
- - **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.
- ## Navigation
- 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.
- 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.
- 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.
- ## Top-level structure
- ```
- references/
- ├── 00-navigation.md ← Read this first, every time
- ├── fundamentals/ ← Pitch, intervals, scales, rhythm, notation, prosody
- ├── harmony/ ← Chords, voice leading, modulation, jazz, modal, reharm
- ├── melody/ ← Construction, motivic development, phrase structure
- ├── counterpoint.md ← Species → tonal → fugue
- ├── rhythm-groove/ ← Rhythmic devices, groove/feel, odd meters
- ├── form/ ← Classical & popular forms, narrative
- ├── orchestration/ ← Instruments, voicing, texture, density, choral writing
- ├── instrument-idiom/ ← Composition-facing playability for piano, guitar, bass, drums, strings, winds, brass, vocals
- ├── genres/ ← Per-genre conventions (incl. Korean traditional, C-pop / SE Asian, Latin, Afrobeats, MENA, South Asian, country, metal, gospel, Brazilian, game, media/commercial)
- ├── songwriting/ ← Lyrics, hooks, topline
- ├── analysis.md ← Roman numeral, form, Schenker, set theory
- ├── techniques/ ← Theme & variation, 20th C., constraint-based, microtonal, algorithmic / AI-assisted
- ├── production-aware/ ← Pre-production, composition-mix interface, energy
- ├── research/ ← Web trends, user listening context, regional trend evolution, reference digging, style/copyright guardrails
- ├── creative-workflows/ ← Musical brainstorming, answer calibration, revision loops, and user-agent collaboration patterns
- ├── validation/ ← Release readiness, Phase B/C records, RC packaging, and prompt smoke tests
- ├── source-bibliography.md ← Maintainer-facing source map and verification guide
- ├── workflow.md ← Starting, revising, hybrid-genre advising
- ├── critique-and-feedback.md ← Evaluating user's existing work (critique mode)
- └── teaching-composition.md ← Pedagogy mode, learning paths, exercises
- scripts/
- └── music_theory_sanity_check.py ← Optional validation and regression helper for maintainers
- assets/
- ├── progressions-catalog.md
- ├── response-templates.md
- ├── diagnostic-checklists.md
- ├── trend-and-reference-matrices.md
- ├── musical-brainstorming-cards.md
- ├── session-brief-and-decision-log.md
- ├── web-search-cheatsheet.md
- ├── chord-symbol-ambiguity-and-parsing.md
- ├── scale-degree-spelling-cheatsheet.md
- ├── music-theory-audit-rubric.md
- ├── cadence-reference.md
- ├── modes-cheatsheet.md
- ├── intervals-and-scale-formulas.md
- ├── jazz-voicings.md
- ├── form-templates.md
- └── chord-symbol-conventions.md
- ```
- ## Typical response workflow
- 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.
- 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.
- 3. **Read `references/00-navigation.md`** to find the relevant reference files.
- 4. **Load the minimal set** of reference files needed.
- 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).
- 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").
- 7. **Stop before over-explaining.** A concise, useful answer beats a comprehensive lecture.
- ## Notation conventions
- Use these consistently throughout the skill:
- - **Chord symbols** (lead-sheet / jazz style): `Cmaj7`, `Dm7`, `G7♭9`, `F♯dim7`, `B♭/D` (slash chord), `Cmaj7♯11`.
- - **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`).
- - **Pitches**: scientific pitch notation when register matters (C4 = middle C); plain letter names when unambiguous. Sharp = `♯`, flat = `♭`, double-sharp = `𝄪`, double-flat = `𝄫`.
- - **Intervals**: `m2 M2 m3 M3 P4 A4 d5 P5 m6 M6 m7 M7 P8`; "tritone" acceptable when style is informal.
- - **Scale degrees**: `^1 ^2 ^3 ...` when concise; "tonic / supertonic / mediant / subdominant / dominant / submediant / leading tone" in prose.
- - **Tempo**: BPM (`120 BPM`); `♩=120` when discussing notation.
- ## Genre framing — always required
- The same musical question has different answers in different genres. Before applying any technique, identify the genre frame:
- - Classical (which period?)
- - Jazz (which sub-style?)
- - Pop / rock / indie
- - Hip-hop / R&B / neo-soul
- - Electronic (which sub-style?)
- - Film / TV (what dramatic context?)
- - Game / interactive media (what platform / interactive system?)
- - Advertising / podcast / branded content / trailer / library music
- - K-pop / J-pop
- - C-pop / Cantopop / T-pop / V-pop / OPM / Indo-pop
- - Latin pop / reggaeton / urbano
- - Brazilian pop / MPB / samba-pop / funk carioca
- - Afrobeats / amapiano
- - South Asian film-pop / raga-derived pop
- - MENA pop / maqam-adjacent fusion
- - Korean traditional (*gugak*) and K-trad fusion
- - Country / Americana / roots
- - Metal / punk / hardcore
- - Gospel / CCM / worship
- - Folk / roots / tradition-specific writing
- - Regional scene starters and local-pop idioms
- - Minor / microgenre / hybrid scenes
- - Musical theatre
- 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.
- ## Extensibility
- This skill is designed to grow. To add new content:
- 1. **New genre or sub-genre**: add `references/genres/<name>.md`, update `00-navigation.md`'s genre table.
- 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.
- 3. **New cheatsheet / matrix asset**: add to `assets/`, update `00-navigation.md`'s asset map.
- 4. **New instrument idiom**: add `references/instrument-idiom/<instrument>.md`, update `instrument-idiom/overview.md` and `00-navigation.md`.
- 5. **New current-research workflow**: add to `references/research/`, include a snapshot note, update `00-navigation.md`, and link from related genre files.
- 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.
- 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.
- 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.
- 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`.
- ## Honesty about gaps
- 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)
- [English](./README.md) | [한국어](./README.ko.md)
- # Music Composition Agent Skill
-    
- A modular knowledge and workflow skill for an AI music-composition assistant.
- 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.
- **Current release:** `v1.0`
- **Release date:** `2026-04-27`
- ---
- ## Installation
- The simplest way is via the [`skills` CLI](https://www.npmjs.com/package/skills) (requires Node.js):
- ```bash
- 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):
- ```bash
- 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.
- ---
- ## Does it work?
- Two benchmarks ship with v1.0:
- **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.
- 
- **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`.
- 
- 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).
- ---
- ## What this skill is for
- Use this skill when an AI agent needs to help with:
- - composition brainstorming
- - chord progressions and harmonic direction
- - melody, motif, phrase, and topline writing
- - song forms, transitions, and narrative structure
- - rhythm, groove, meter, and feel
- - orchestration, arrangement, voicing, and instrument idiom
- - genre-aware writing across pop, jazz, classical, game, media, regional, traditional, and hybrid styles
- - critique and revision of a work in progress
- - teaching music concepts in a practical composition-first way
- - current music trend research and reference-track digging
- - user-agent collaborative workflows across multiple turns
- 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.
- ---
- ## Core design philosophy
- The skill is built around a few practical principles:
- 1. **Composition is decision-making, not rule-following.**
- Music theory is treated as a map of possible effects, not a list of commandments.
- 2. **Give playable, actionable output.**
- Prefer concrete examples such as chord charts, scale-degree melodies, groove sketches, voicing suggestions, and revision blocks.
- 3. **Preserve user agency.**
- Offer options, explain tradeoffs, and let the user choose a direction.
- 4. **Use only the references needed.**
- The agent should usually start with `SKILL.md`, route through `references/00-navigation.md`, and load only the most relevant 1–3 files.
- 5. **Treat current music trends as research tasks.**
- Static genre files provide stable craft conventions. Recent artists, charts, platform norms, and scene-specific references should be checked through active web research.
- 6. **Avoid shallow cultural shortcuts.**
- 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.
- ---
- ## Repository structure
- ```text
- .
- ├── SKILL.md
- ├── MAINTENANCE.md
- ├── RELEASE-ROADMAP.md
- ├── KNOWN-LIMITATIONS.md
- ├── RELEASE-NOTES-v1.0.md
- ├── VALIDATION-v1.0.md
- ├── assets/
- ├── references/
- │ ├── 00-navigation.md
- │ ├── creative-workflows/
- │ ├── form/
- │ ├── fundamentals/
- │ ├── genres/
- │ ├── harmony/
- │ ├── instrument-idiom/
- │ ├── melody/
- │ ├── orchestration/
- │ ├── production-aware/
- │ ├── research/
- │ ├── rhythm-groove/
- │ ├── songwriting/
- │ ├── techniques/
- │ └── validation/
- └── scripts/
- └── music_theory_sanity_check.py
- ```
- ### Important files
- | File | Purpose |
- |---|---|
- | `SKILL.md` | Root operating instructions for the agent. Start here. |
- | `references/00-navigation.md` | Routing map for choosing the right reference files. |
- | `assets/` | Short cheat sheets and response templates for quick use. |
- | `references/creative-workflows/` | Brainstorming, revision, answer calibration, and user-agent collaboration. |
- | `references/research/` | Web trend research, reference-track digging, streaming-service-aware research, and style/copyright guardrails. |
- | `references/genres/` | Genre and regional starter guides. |
- | `references/instrument-idiom/` | Composition-facing playability and idiomatic writing guides. |
- | `references/validation/` | Release readiness, smoke tests, correctness passes, and packaging checklists. |
- | `scripts/music_theory_sanity_check.py` | Regression checker for links, known theory errors, risky terminology, snapshot notes, and required files. |
- ---
- ## Suggested agent workflow
- For most user requests:
- ```text
- 1. Read SKILL.md.
- 2. Use references/00-navigation.md to identify the smallest useful document set.
- 3. Load only the relevant reference files, usually 1–3.
- 4. Generate concrete musical output.
- 5. Explain why the choices work.
- 6. Offer a small number of next-step options.
- ```
- For example:
- | User request | Likely routing |
- |---|---|
- | “Give me a sad but not cliché progression.” | `harmony/functional-harmony.md`, `harmony/modal-harmony.md`, `assets/progressions-catalog.md` |
- | “The chorus does not hit.” | `assets/diagnostic-checklists.md`, `songwriting/hooks-and-memorability.md`, `production-aware/energy-and-dynamics.md` |
- | “Make this more playable on guitar.” | `instrument-idiom/guitar.md`, plus the relevant harmony or arrangement file |
- | “Brainstorm three directions.” | `creative-workflows/musical-brainstorming.md`, `assets/musical-brainstorming-cards.md` |
- | “Find current J-pop references.” | `research/web-music-trend-research.md`, `research/reference-track-digging.md`, `assets/web-search-cheatsheet.md` |
- | “Use my playlist as a reference.” | `research/user-listening-context-and-streaming-services.md`, `assets/trend-and-reference-matrices.md` |
- ---
- ## Currentness policy
- Some files include a snapshot note. These files contain information that can become outdated, especially around:
- - current genre trends
- - charts and streaming-platform behavior
- - artist references
- - regional scenes
- - AI-assisted music tools
- - copyright and policy developments
- 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.
- Useful research files:
- ```text
- references/research/web-music-trend-research.md
- references/research/reference-track-digging.md
- references/research/user-listening-context-and-streaming-services.md
- references/research/regional-trend-evolution-analysis.md
- references/research/style-reference-and-copyright.md
- assets/web-search-cheatsheet.md
- ```
- ---
- ## Style, originality, and copyright guardrails
- This skill is intended to help generate original musical ideas. It should not be used to copy protected expression from existing songs or artists.
- When a user asks for a specific artist or song style, the agent should translate the reference into craft variables such as:
- - tempo range
- - groove type
- - harmonic density
- - form
- - vocal range and phrasing style
- - arrangement density
- - instrumentation
- - energy curve
- - production-era cues
- The agent should avoid reproducing or imitating protected elements such as:
- - melody
- - lyrics
- - distinctive riffs
- - samples
- - signature producer tags
- - highly specific vocal identity
- - recognizable arrangement sequences from a particular recording
- See:
- ```text
- references/research/style-reference-and-copyright.md
- KNOWN-LIMITATIONS.md
- ```
- ---
- ## Cultural and regional specificity
- 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.
- When working with culturally specific material, prefer:
- ```text
- specific tradition / region / language / function / rhythm / instrument idiom / performance context
- ```
- Instead of vague labels such as:
- ```text
- generic world flavor / ethnic color / Asian flavor / Middle Eastern flavor
- ```
- Relevant files include:
- ```text
- references/genres/korean-traditional.md
- references/genres/folk-roots-and-traditions.md
- references/genres/mena-pop.md
- references/genres/south-asian-film-pop.md
- references/genres/regional-scene-starters.md
- references/research/regional-trend-evolution-analysis.md
- ```
- ---
- ## Validation
- The v1.0 package passed the release validation recorded in:
- ```text
- VALIDATION-v1.0.md
- references/validation/first-release-readiness.md
- references/validation/phase-b-correctness-pass.md
- references/validation/phase-c-smoke-test-results.md
- ```
- To run the sanity checker:
- ```bash
- python scripts/music_theory_sanity_check.py
- ```
- The checker looks for issues such as:
- - broken internal Markdown references
- - known high-risk music-theory regressions
- - risky cultural shortcut terminology
- - missing snapshot notes in current-sensitive files
- - required release and validation files
- - selected interval, mode, chord-symbol, and altered-dominant sanity checks
- This checker is a regression tool, not a complete proof of musical correctness.
- ---
- ## Maintenance
- Before changing the repository:
- 1. Read `MAINTENANCE.md`.
- 2. Update `references/00-navigation.md` when adding or moving files.
- 3. Keep high-use assets concise and accurate.
- 4. Use snapshot notes for current-sensitive files.
- 5. Run `scripts/music_theory_sanity_check.py`.
- 6. Record substantial validation work in the relevant validation document.
- Recommended versioning:
- | Change type | Suggested version |
- |---|---|
- | Typo, link, or small validation-script fix | `v1.0.x` |
- | P0/P1 correctness hotfix | `v1.0.x` hotfix |
- | New genre, workflow, or research documents | `v1.1` |
- | Larger parser/evaluation harness improvements | `v1.1` or `v1.2` |
- | Major structure change or file reorganization | `v2.0` candidate |
- ---
- ## Known limitations
- See `KNOWN-LIMITATIONS.md` for the full list.
- In brief, this skill does not directly provide:
- - audio transcription
- - DAW control
- - MIDI export
- - audio mixing or mastering
- - legal advice
- - guaranteed current trend knowledge without web research
- - exhaustive expertise in every local or traditional music practice
- ---
- ## License
- This repository uses a split license:
- - Skill documents, references, assets, release notes, and validation documents are licensed under **Creative Commons Attribution 4.0 International (CC BY 4.0)**.
- - Code in `scripts/` is licensed under the **MIT License**.
- See `LICENSE.md` for details.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.