Chorus
Chorus-AIDLC/Chorus
Chorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
J-pop as a style layer (日式流行风格层) - the chorus-centred design discipline that distinguishes Japanese pop from Western pop.
MITAuto-check passed
Install Mc Style Jpop
$ npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-style-jpop --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/music-composition/skills/mc-style-jpop .claude/skills/mc-style-jpop && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mc-style-jpop" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpop into .claude/skills/mc-style-jpop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-style-jpop", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpopType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-style-jpop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/music-composition/skills/mc-style-jpop .agents/skills/mc-style-jpop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mc-style-jpop" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpop into .agents/skills/mc-style-jpop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-style-jpop", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-style-jpop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/music-composition/skills/mc-style-jpop .cursor/skills/mc-style-jpop && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mc-style-jpop" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpop into .cursor/skills/mc-style-jpop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-style-jpop", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jtydhr88/music-composition-skills.git --path plugins/music-composition/skills/mc-style-jpop--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-style-jpop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/music-composition/skills/mc-style-jpop .gemini/skills/mc-style-jpop && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mc-style-jpop" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpop into .gemini/skills/mc-style-jpop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-style-jpop", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jtydhr88/music-composition-skills mc-style-jpopInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/music-composition/skills/mc-style-jpop .github/skills/mc-style-jpop && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mc-style-jpop" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpop into .github/skills/mc-style-jpop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-style-jpop", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jtydhr88/music-composition-skills mc-style-jpop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/music-composition-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/music-composition/skills/mc-style-jpop .opencode/skills/mc-style-jpop && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mc-style-jpop" agent skill from https://github.com/jtydhr88/music-composition-skills/tree/main/plugins/music-composition/skills/mc-style-jpop into .opencode/skills/mc-style-jpop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mc-style-jpop", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mc-style-jpop- GitHub stars
- 154
- Token cost
- ~1.6k tokens
- SKILL.md length
- 428 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- MIT
At a glance
J-pop as a style layer (日式流行风格层) - the chorus-centred design discipline that distinguishes Japanese pop from Western pop.
- Works in 10 steps: 动笔前必填 → ★ 移植表 → 副歌为什么听起来像副歌 → …
- Arranging J-pop
- SKILL.md covers 按任务读哪几节, 边界, 1. 动笔前必填 and 2. ★ 移植表, plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mc Style Jpop is an agent skill from jtydhr88/music-composition-skills. J-pop as a style layer (日式流行风格层) - the chorus-centred design discipline that distinguishes Japanese pop from Western pop. Why the sabi sounds like the sabi and the first-aid kit when it will not lift, the two maximization strategies (exposure and anticipation) and the boredom trade-off that governs them, the internal structure of a chorus and the two ways to build one, the role and the optional nature of the o-sabi, the B-melo as a genuinely Japanese invention, and the transfer table for what survives outside…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Professional agent skills for composing and arranging popular music. The licence is MIT.
When your agent uses it
- Arranging J-pop
- Anime-adjacent pop
- A chorus does not lift
- Deciding whether to add a bridge
Example prompts
- “/mc-style-jpop”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7adca0c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mc Style Jpop loads about 1.6k tokens when it runs. Until then it costs about 188 tokens; SKILL.md has 428 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jtydhr88/music-composition-skills at commit 7adca0c, republished under its MIT licence (© jtydhr88). 428 words, ~1,647 tokens.
Download SKILL.mdSave it as
.claude/skills/mc-style-jpop/SKILL.md (or your agent's skills folder).- name
- mc-style-jpop
- description
- J-pop as a style layer (日式流行风格层) - the chorus-centred design discipline that distinguishes Japanese pop from Western pop. Why the sabi sounds like the sabi and the first-aid kit when it will not lift, the two maximization strategies (exposure and anticipation) and the boredom trade-off that governs them, the internal structure of a chorus and the two ways to build one, the role and the optional nature of the o-sabi, the B-melo as a genuinely Japanese invention, and the transfer table for what survives outside J-pop. Use when writing or arranging J-pop or anime-adjacent pop, when a chorus does not lift, when deciding whether to add a bridge, or when borrowing a J-pop device into another style. 日式流行、Jpop、サビ、副歌、B メロ、大サビ、落ちサビ、动漫歌。
日式流行风格层（J-POP）
J-POP 与欧美流行最根本的差别不在和声，在"整首歌为副歌服务"的程度。
欧美流行：主歌与副歌是两个内容。 J-POP：主歌与 B メロ 是副歌的铺台面（お膳立て）。
这个差别产生了一整套 J-POP 特有的设计纪律，就是这个 skill。
按任务读哪几节
| 任务 | 读 |
|---|---|
| 判断 J-POP 手法能不能搬出去 | ★ §2 移植表 |
| 副歌"起不来" | ★ §4 急救包 |
| 副歌听着不像副歌 | §3 |
| 副歌太多/太少 | §5 曝光与厌腻的权衡 |
| 进副歌前不够抓人 | §6 期待 |
| 副歌虎头蛇尾 | §7 |
| 要不要加 C メロ / 大サビ | ★ §8（多数情况的答案是不加） |
边界
| 不归这里 | 归哪 |
|---|---|
| 段落术语的定义与映射 | mc-form §1（★ 大サビ 映射成 Bridge） |
| 曲式模板与倒推设计 | mc-form §2、§5 |
| 王道进行、小室、卡农等和声语汇 | mc-progressions（★ 它们已经进了通用层） |
| 能量曲线、减法、hook 布局 | mc-arrangement-arch |
| 打ち込み 的实现 | mc-rhythm-section |
| 演唱设计 | mc-vocal-direction |
| 词曲对齐（符割り、字余り） | 作词库 lyric-writing |
★ 一个提醒：日式作曲法里的通用部分都在通用层（L1 的旋律/和声/曲式，L2 的打ち込み/演唱）。 本 skill 只写"确实是 J-POP 特有"的部分。
1. 动笔前必填
| 必填 | 问法 |
|---|---|
| ① 副歌在哪、长什么样 | ★ 先写副歌。J-POP 是倒推设计的（mc-form §5） |
| ② 副歌要出现几次 | §5。这是曝光与厌腻的权衡，要主动决定 |
| ③ 进副歌前做什么 | §6。这一处比副歌本身还重要 |
| ④ 要不要 C メロ | ★ §8。默认答案是不要 |
2. ★ 移植表
| 手法 | 可搬出 J-POP 吗 | 说明 |
|---|---|---|
| A–B–サビ 三段构成 | ✅ 可搬，已被华语流行全面采用 | mc-form §2.2 |
| B メロ（预副歌） | ✅ ★ 可搬，而且是 J-POP 对世界流行最大的贡献之一 | 它给了"渐强"一个专门的段落 |
| 和声语汇（王道/小室/卡农/丸サ） | ✅ 可搬 | 已在 mc-progressions |
| 落ちサビ（稀薄副歌） | ✅ 可搬，且极有效 | 它是 mc-arrangement-arch §3 减法的一个具体形态 |
| 副歌最大化（曝光策略） | ⚠️ 半搬 | ★ 欧美流行的副歌重复次数明显更少。搬过去容易显得"啰嗦" |
| 大サビ（C メロ） | ⚠️ 半搬 | 它对应英美的 bridge，但性格更内省、常带半速感 |
| キメ（插旗句） | ⚠️ 半搬 | 在摇滚里通用；在慢歌里是 J-POP 味 |
| 頭サビ（开场即副歌） | ✅ 可搬 | 短视频时代反而更通用了 |
| "整首为副歌服务"这个哲学本身 | ❌ ★ 不可搬 | 欧美/独立/爵士的主歌是有独立价值的。照搬会让主歌变成空洞的过场 |
★ 判据：
可以搬走它的装置（B メロ、落ちサビ、頭サビ）， 但不要搬走它的世界观（主歌只是铺垫）。
3. 副歌为什么听起来像副歌
基本原理：サビ = 全曲最高扬的点，也是歌词里最需要传达信息的地方。
3.1 旋律曲线
A 段唱得低 → B 段逐步上行 → サビ 跳到高位并停在那里。
★ 在结构典型的歌里，就算清唱也能听出副歌在哪。
这是一条自检动作：把旋律清唱一遍。听不出副歌在哪，副歌就没写成。
3.2 伴奏跟着曲线走
| 轴 | A 段 | サビ |
|---|---|---|
| 纵轴（厚度） | 薄而柔 | 强到不会输给全声的人声，用满从低到高的音域 |
| 横轴（时间密度） | 以四分/八分音符为主 | 加入十六分音符乐句抬高密度 |
3.3 ★ 一个容易漏的细节
副歌旋律有起有伏时，旋律下行的部分最容易被伴奏埋掉—— 在那些位置故意让伴奏留空隙。
这条对应 mc-texture-layering §3 的深度线索：
旋律下行时它在"高/快"两条线索上都输了，必须靠留白补回来。
3.4 副歌各遍结尾都一样时
各遍编曲和结尾都差不多时，最后一遍会显得"到底了却没有再往上"。藤谷给的做法是把最后一遍拆成前后两半做对比：前半先把热度压下去（乐器减到只剩钢琴或主奏），听众才会把后半重新冲上来的亮点听成"更高"而不是"又来一次"；后半配合亮点一次冲上去，旋律可以不完全照谱、带一点即兴（fake）味，弦乐等声部继续往高音域走（藤谷 p0069）。
篇幅够的话，也可以让最后一遍不与前面等长，做成两倍长度，同样是前半安静、后半接近副歌处愈加热闹（藤谷 p0062）。两种做法的共同点是靠"先压下去再顶上去"制造差异，不是单靠反复堆同一个音区。
4. ★ 急救包："副歌起不来"
按这个顺序试：
| # | 做法 | 注意 |
|---|---|---|
| 1 | 人声上不去 → 叠高音区乐器 | ★ 别埋掉人声：把高音塞进人声的空隙里 |
| 2 | 加低音区乐器和节奏型乐器抬密度 | |
| 3 | ★★ 终极法宝 = "人声" | 加和声或 aah/ooh/hah 式的合唱——副歌立刻就像副歌了 |
★★ 人声的能量效率大约是乐器的 3 倍。 乐器费很大劲才能达到的高扬，人声轻松就能做到。
★ 这条是本 skill 最实用的一句。 "副歌不够炸"的第一反应不该是加乐器，是加人声。
冷知识：英文用 "chorus" 指副歌，词源就是最大高潮处大家一起唱。
5. 最大化策略 A：曝光
人对反复听到的东西产生依恋，第一策略是让副歌被听到尽可能多次：
- 开场用 頭サビ
- 尽量压缩间奏与平歌
- 堆 1 サビ、2 サビ、3 サビ、4 サビ
- 最后一节用
A−B−C−C（−C−C），反复副歌造全曲大高潮
5.1 ★ 但这是一个权衡
"整首都是副歌"会腻—— 流行编曲就是"如何让人尽可能多地听到副歌而不厌烦"这个游戏。 副歌太少记不住，太多则乏味。
防腻装置：
| 装置 | 做法 |
|---|---|
| 同旋律换编制 | 第 3 遍副歌突然变安静 = 落ちサビ；頭サビ 用适合开场的编制（薄伴奏+慢速+自由速度 = 叙述式导入，或原样演奏 = 炫目开场） |
| 转调 | 同编制下靠换调避免单调（→ mc-modulation，★ 但注意它的套路警戒线 §6） |
6. ★ 最大化策略 B：期待
进副歌前的那一段最要紧。 与其懒洋洋地滑进副歌，在进入前制造一个变化，抓耳程度高得多。
| 做法 |
|---|
| 突然全停（ブレイク），然后"砰"地进副歌 |
| 和弦上加一个小转折 |
| 简单的八分音符渐强 |
| 副歌前的鼓 fill —— 对熟悉这首歌的听众，情绪会随 fill 提前上来 |
这些的本质都是制造"来るぞ来るぞ"（来了来了）的期待。
Show full SKILL.md (165 more words)Show less
6.1 ★ 一条警告
副歌的编曲当然要有吸引力，但如果平歌（主歌）没有同等的吸引力， 听众根本撑不到副歌。
这与 §2 移植表最后一行呼应："主歌只是铺垫"这个世界观有它的代价。
7. 副歌的内部结构
- 副歌作为一个乐节，内部高潮仍遵守"2/3–3/4 处"规则
- ★ 防止竜頭蛇尾（虎头蛇尾）：即使副歌开头就在高点， 也要检查后半是否还有充分的高潮、能否实质地收住—— "重复部分动机、再次推起来，不要让它松掉"
7.1 两种做副歌的方式
| 型 | 说明 |
|---|---|
| 口号型 | 建立在短动机重复上（摇滚常见，听一遍就记住） |
| 歌い上げる型（全声唱上去） | 长旋律——这是日语"サビ"一词的本意（melo = sabi 形），日本流行与抒情曲常见 |
7.2 适合副歌的动机构成
这两种只是给内部乐句排布贴标签，不是另一套独立技法：怎么把动机重复、推起来、在后半收住，仍然按本节开头"2/3–3/4 处"和"防止竜頭蛇尾"两条来做，曲线的走向见 §3.1。
| 构成 | 效果 |
|---|---|
| a a b a | 最后再现，满足感强 |
| a b a c | a 抓注意力，c 承担大高潮（c 落在 2/3–3/4 处附近，呼应上面那条规则） |
7.3 ★ 落ちサビ 的实战范例
（抒情曲）
第 2 番副歌之后，后半的伴奏做得完全满 → 听众预期第 3 番也会轰进来 → 结果只给一个钢琴 + 人声的耳语式副歌 → 2 或 4 小节后乐队一起轰进来 —— 极其动人。
★ 这是"利用期待再翻盘"（mc-melody §8.2）的教科书实例。
8. ★ 大サビ（C メロ）：默认不加
8.1 它是什么
| 项 | 说明 |
|---|---|
| 作用 | 一句"ところで"（话说回来）或"だけど"（可是……）的旁白/另一视角，给歌层次深度 |
| 性格 | 常是内省、收敛的旋律；快歌里常把时值拉长，听起来像只有这一段掉进了半速 |
| ★ 另一家的说法 | 藤谷（p0060）：D 旋律是副歌的衍生型，靠加入若干第一次出现的要素再造一个高潮，这里的气氛不太可能平静。两家并排：一个当另一视角的旁白写，一个当第二高潮写。判据是它后面那个副歌要不要靠对比才有分量，要就走内省，不要就走衍生 |
| 手法参考 | 静态的音高运动 + 转调 + 以小三度关系和弦为主的和声 |
| 位置 | ★ 它的功能是"主歌"，所以后面一定跟一个副歌。情绪平静下来之后，后面那个副歌的高潮才更有分量 |
8.2 ★ 它不是必须的
大サビ 不是强制的： 仅仅出于习惯加上的大サビ，反而会削弱歌曲的势头。
先确认各节的副歌重复是否真的让人觉得予定調和，再决定加不加。
自检动作：把 C メロ 拿掉听一遍。如果没变差，就别加。
9. 与 ARR-SPEC 的字段对应
| 字段 | 本 skill |
|---|---|
meta.style_layer | mc-style-jpop |
form[] | §3、§5；★ 大サビ 的 name 填 Bridge（mc-form §7） |
energy_curve | §3.1 的曲线：A 低 → B 升 → サビ 高位 |
subtraction_events | ★ 落ちサビ 就是一个减法事件（§7.3） |
vocal.stacking | §4 的第 3 条——加和声/合唱是副歌起不来的首选解 |
vocal.chorus_variation | §5.1 防腻装置（lint #16） |
10. 写完后必过
- 清唱能听出副歌在哪（§3.1）
- 副歌旋律下行处，伴奏留了空隙
- 副歌起不来时，先试了加人声而不是加乐器
- 副歌出现次数是主动决定的，且配了防腻装置
- 进副歌前那一段做了变化，不是滑进去的
- 主歌本身有吸引力，不是空洞的铺垫
- 副歌后半也有高潮，没有虎头蛇尾
- ★ 加了 C メロ 的话，拿掉听过一遍确认它有用
- 往别的风格搬时，查过 §2——没有把"主歌只是铺垫"一起搬走
附：来源
- 日式包
jp-song-structure§IV、§V——本 skill 的全部主干。 ★ 该包的其余部分已升到通用层： 段落术语与曲式模板 →mc-form；hook 与结尾 →mc-arrangement-arch； 反予定調和 →mc-melody§8；段落对比与逐段编制表 →mc-formreference.md。 - 日式风格分类
- 图解编曲
© jtydhr88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/music-composition/skills/mc-style-jpop of jtydhr88/music-composition-skills.
Open the folder on GitHubat commit 7adca0c
Compare with similar skills
Mc Style Jpop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mc Style Jpop this skilljtydhr88/music-composition-skills | 154 | — | ~1.6k | Automated safety check: Pass | MIT | |
| ChorusChorus-AIDLC/Chorus | 1.2k | — | ~6.5k | Automated safety check: Notes | AGPL-3.0 | |
| ChorusChorus-AIDLC/Chorus | 1.2k | — | ~8.8k | Automated safety check: Pass | AGPL-3.0 | |
| ChorusChorus-AIDLC/Chorus | 1.2k | — | ~9.1k | Automated safety check: Notes | AGPL-3.0 | |
| Chorus CLIChorus-AIDLC/Chorus | 1.2k | — | ~1.2k | Automated safety check: Notes | AGPL-3.0 | |
| Chorus CLIChorus-AIDLC/Chorus | 1.2k | — | ~915 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Chorus
Chorus-AIDLC/Chorus
Chorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
Chorus
Chorus-AIDLC/Chorus
Chorus AI Agent collaboration platform for Hermes Agent — overview, common tools, Hermes setup, and routing to stage-specific skills.
Chorus CLI
Chorus-AIDLC/Chorus
How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp.
Chorus CLI
Chorus-AIDLC/Chorus
How to install, configure, and use the chorus CLI — install it, manage agents with chorus agents (add/remove/list), the connection environment variables, and MCP operations via chorus mcp.
Chorus Yolo
Chorus-AIDLC/Chorus
Full-auto AI-DLC pipeline — from prompt to done. An agent skill from Chorus-AIDLC/Chorus.
More from jtydhr88/music-composition-skills
All 29 skills in this repoMc AI Tell Audit
jtydhr88/music-composition-skills
The post-generation AI-tell audit (AI 味诊断). An agent skill from jtydhr88/music-composition-skills.
Mc Arrangement Arch
jtydhr88/music-composition-skills
Arrangement architecture (编曲结构学) - the shape of a track over time rather than its notes.
Mc Case Studies
jtydhr88/music-composition-skills
The corpus layer (语料层) - how real recordings are made to testify for or against the textbook rules.
Mc Development
jtydhr88/music-composition-skills
Thematic development (乐思发展层) - what the theme is and what each section does with it.
Mc Form
jtydhr88/music-composition-skills
Song form and section design (曲式与段落) - the terminology, the standard templates, and how to build a setsu backwards from the chorus.
Mc Melody
jtydhr88/music-composition-skills
Melody writing (旋律法) - what a melodic line expresses and how to make it singable.
Questions about Mc Style Jpop
What does Mc Style Jpop do?
J-pop as a style layer (日式流行风格层) - the chorus-centred design discipline that distinguishes Japanese pop from Western pop. Mc Style Jpop is an agent skill from jtydhr88/music-composition-skills. J-pop as a style layer (日式流行风格层) - the chorus-centred design discipline that distinguishes Japanese pop from Western pop.
When should I use Mc Style Jpop?
Mc Style Jpop fits situations like: arranging J-pop; anime-adjacent pop; A chorus does not lift; deciding whether to add a bridge.
How do I install Mc Style Jpop in Claude Code?
Run `npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a claude-code`. Or copy the skill folder (plugins/music-composition/skills/mc-style-jpop in jtydhr88/music-composition-skills) into .claude/skills/mc-style-jpop in your project. Claude Code loads it when a task matches its description.
How do I install Mc Style Jpop in Codex?
Run `npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a codex`. Or copy the skill folder (plugins/music-composition/skills/mc-style-jpop in jtydhr88/music-composition-skills) into .agents/skills/mc-style-jpop in your project. Codex loads it when a task matches its description.
Can I use Mc Style Jpop in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jtydhr88/music-composition-skills --skill mc-style-jpop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mc-style-jpop, .gemini/skills/mc-style-jpop, .github/skills/mc-style-jpop and .opencode/skills/mc-style-jpop in your project.
What does Mc Style Jpop need to run?
SKILL.md names no scripts, command-line tools or credentials: Mc Style Jpop is instructions for the agent only.
Does Mc Style Jpop access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mc Style Jpop safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mc Style Jpop use?
Mc Style Jpop is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mc Style Jpop use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mc Style Jpop?
Skills that share tags, products or a category with Mc Style Jpop: Chorus (Chorus-AIDLC/Chorus, 1.2k stars), Chorus (Chorus-AIDLC/Chorus, 1.2k stars), Chorus (Chorus-AIDLC/Chorus, 1.2k stars) and Chorus CLI (Chorus-AIDLC/Chorus, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mc Style Jpop?
jtydhr88 (a GitHub user) maintains it in jtydhr88/music-composition-skills, which has 154 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on September 22, 2026.
Source: jtydhr88/music-composition-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.