[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74ET2KQ5CC4JCFGBSG0YXM3":3,"skill-same:01M74ET2KQ5CC4JCFGBSG0YXM3":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M74ET2KQ5CC4JCFGBSG0YXM3","consolidate",null,"Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.","MoonshotAI\u002Fkimi-code","MoonshotAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129152888?v=4","01M74ERZMTV9BR82QKWAF5NAVA","Moonshot AI","01M74ERZND3KECTZ02YW0FYJSR",8226,"MIT","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Fconsolidate\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: consolidate\ndescription: Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.\ndisable-model-invocation: true\n---\n\n# Consolidate sub-skills (`sub-skill.consolidate`)\n\nExecute the reorganization by moving user-specified skills into a parent bundle, forming a sub-skill hierarchy.\n\n## When to use\n\n- The user has approved a grouping proposal (typically from `sub-skill.review`) and wants to apply it.\n- Migrating standalone skills into a new or existing parent bundle.\n\n## Process\n\n1. **Confirm the plan.** Restate which skills will move and where, and ask the user to confirm **before** making any file changes.\n2. **Back up every original skill directory.** Before moving anything, create a timestamped backup of each skill directory that will be modified.\n   - For a skill at `\u003Croot>\u002F\u003Cskill-name>\u002FSKILL.md`, back up the entire `\u003Cskill-name>` directory:\n     ```bash\n     cp -r \u003Cskill-name> \"\u003Cskill-name>.$(date +%Y%m%d-%H%M%S).bak\"\n     ```\n   - Keep all backups; never overwrite an existing backup file.\n3. **Create or update the parent bundle.**\n   - If the parent does not exist, create `\u003Cparent-name>\u002FSKILL.md` with `has-sub-skill: true` in the frontmatter.\n   - If the parent already exists, ensure its frontmatter includes `has-sub-skill: true`.\n4. **Move child skills into the parent.** Move each child skill's entire directory under the parent bundle.\n   - Example: `web-search\u002F` → `web-research\u002Fweb-search\u002F`\n5. **Keep documentation directory alignment.** When moving documentation, references, examples, assets, or other payload directories, align them with the new skill directory layout.\n   - Preserve relative links from `SKILL.md` to files such as `references\u002F`, `assets\u002F`, `examples\u002F`, or templates.\n   - If a child skill moves from `\u003Croot>\u002F\u003Cchild>\u002F` to `\u003Croot>\u002F\u003Cparent>\u002F\u003Cchild>\u002F`, its documentation payload should move with that child unless the approved plan says otherwise.\n   - Do not leave documentation in the old location or merge unrelated documentation directories together.\n6. **Verify the result.** List the new directory structure and confirm each moved skill still has a valid `SKILL.md` with required frontmatter (`name` and `description`). Check documentation directory alignment and relative links after the move.\n7. **Report the change.** Summarize what was moved, the new structure, any documentation directories that moved, and where backups are located.\n\n## Don'ts\n\n- **Never move skills without backing up first.**\n- **Never overwrite an existing backup** — always use a fresh timestamped suffix.\n- **Don't drop frontmatter or payload files** during the move; the entire directory must be preserved.\n- **Don't break documentation directory alignment** — references, assets, examples, and templates must stay aligned with the skill directory that uses them.\n- **Don't create deeply nested hierarchies** (3+ levels) unless the user explicitly requests it.\n","# Consolidate sub-skills (`sub-skill.consolidate`)\n\nExecute the reorganization by moving user-specified skills into a parent bundle, forming a sub-skill hierarchy.\n\n## When to use\n\n- The user has approved a grouping proposal (typically from `sub-skill.review`) and wants to apply it.\n- Migrating standalone skills into a new or existing parent bundle.\n\n## Process\n\n1. **Confirm the plan.** Restate which skills will move and where, and ask the user to confirm **before** making any file changes.\n2. **Back up every original skill directory.** Before moving anything, create a timestamped backup of each skill directory that will be modified.\n   - For a skill at `\u003Croot>\u002F\u003Cskill-name>\u002FSKILL.md`, back up the entire `\u003Cskill-name>` directory:\n     ```bash\n     cp -r \u003Cskill-name> \"\u003Cskill-name>.$(date +%Y%m%d-%H%M%S).bak\"\n     ```\n   - Keep all backups; never overwrite an existing backup file.\n3. **Create or update the parent bundle.**\n   - If the parent does not exist, create `\u003Cparent-name>\u002FSKILL.md` with `has-sub-skill: true` in the frontmatter.\n   - If the parent already exists, ensure its frontmatter includes `has-sub-skill: true`.\n4. **Move child skills into the parent.** Move each child skill's entire directory under the parent bundle.\n   - Example: `web-search\u002F` → `web-research\u002Fweb-search\u002F`\n5. **Keep documentation directory alignment.** When moving documentation, references, examples, assets, or other payload directories, align them with the new skill directory layout.\n   - Preserve relative links from `SKILL.md` to files such as `references\u002F`, `assets\u002F`, `examples\u002F`, or templates.\n   - If a child skill moves from `\u003Croot>\u002F\u003Cchild>\u002F` to `\u003Croot>\u002F\u003Cparent>\u002F\u003Cchild>\u002F`, its documentation payload should move with that child unless the approved plan says otherwise.\n   - Do not leave documentation in the old location or merge unrelated documentation directories together.\n6. **Verify the result.** List the new directory structure and confirm each moved skill still has a valid `SKILL.md` with required frontmatter (`name` and `description`). Check documentation directory alignment and relative links after the move.\n7. **Report the change.** Summarize what was moved, the new structure, any documentation directories that moved, and where backups are located.\n\n## Don'ts\n\n- **Never move skills without backing up first.**\n- **Never overwrite an existing backup** — always use a fresh timestamped suffix.\n- **Don't drop frontmatter or payload files** during the move; the entire directory must be preserved.\n- **Don't break documentation directory alignment** — references, assets, examples, and templates must stay aligned with the skill directory that uses them.\n- **Don't create deeply nested hierarchies** (3+ levels) unless the user explicitly requests it.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","54a9e51fcb0531c4dff816e492a8e6d0a598641e","packages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Fconsolidate",1377,"https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code","https:\u002F\u002Fwww.kimi.com\u002Fcode\u002Fdocs\u002F","https:\u002F\u002Fgithub.com\u002FMoonshotAI","https:\u002F\u002Fmoonshot.ai","2026-11-14 19:55:03",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add MoonshotAI\u002Fkimi-code --skill consolidate",{"tool":40,"command":41},"bunx","bunx skills add MoonshotAI\u002Fkimi-code --skill consolidate",{"tool":43,"command":44},"pnpm","pnpm dlx skills add MoonshotAI\u002Fkimi-code --skill consolidate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Fconsolidate\u002FSKILL.md",[],[48,55,61,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M74ETAEBHZ0QS6Y4BT29PKNF","golden-skill","Golden fixture skill","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fmigration-legacy\u002Ftest\u002Ffixtures\u002Fgolden\u002F.kimi\u002Fskills\u002Fgolden-skill\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M74ET9QF6YK6KD5KM2W4XPBD","tools","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Ftools\u002Fskill.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M74ET7K1MXGBYV91558T1VMC","review","Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only — proposes a plan, does not move files.","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Freview\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M74ET036WTFZ4XH9KC2M84KQ","sub-skill","Discover and reorganize the skill inventory into hierarchical sub-skill bundles. Use when the user asks to review, group, or consolidate skills into a parent bundle.","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M74ESXAT6AX5YG29SN3WY83J","write-tui","Use when writing or modifying the kimi-code terminal UI in apps\u002Fkimi-code\u002Fsrc\u002Ftui — components, dialogs\u002Fselectors, slash commands, themes, streaming render, or the KimiTUI controllers. Covers the architecture, where new features go, test placement, the theme system mechanics, and the dialog interaction\u002Fvisual spec (DESIGN.md).","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-tui\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M74ESVWA1JWTTZM9HTREV7PP","write-pr","在 kimi-code 仓库里创建或更新 PR 时使用：如何写出让 reviewer 只读描述就能从逻辑和架构上理解改动的 PR 描述，包括核心思路与结构图、\"行为变化与受影响人群\"表、可视化大纲，以及 UI\u002FUX 变化的截图和录屏。","https:\u002F\u002Fgithub.com\u002FMoonshotAI\u002Fkimi-code\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-pr\u002FSKILL.md",[],[]]