[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARA1P2XJSCZFVZASQD0JE4":3,"skill-same:01M7ARA1P2XJSCZFVZASQD0JE4":53},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7ARA1P2XJSCZFVZASQD0JE4","write-tui",null,"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).","HypoxanthineOvO\u002FVSPi","HypoxanthineOvO","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F95569749?v=4","01M7AR7HCHB63727Q4DSQBSJVD","Yunxiang He","01M7AR7HD8267Q4WKQJ4QZG1XW",6,"MIT","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-tui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-tui\ndescription: 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).\n---\n\n# Write TUI (apps\u002Fkimi-code)\n\nThe terminal UI lives in `apps\u002Fkimi-code\u002Fsrc\u002Ftui`. Before writing TUI code, read `apps\u002Fkimi-code\u002FAGENTS.md` for the always-on **map, module boundaries, and hard constraints** (printable-key decoding, no chalk named colors, etc.). This skill is the **how-to**: architecture orientation, feature routing, test placement, theme mechanics, and the dialog spec.\n\nFor any list dialog, selector, input box, or status\u002Ftoggle list, the interaction and visual rules are normative — see **[DESIGN.md](.\u002FDESIGN.md)** in this folder and follow its self-check list before submitting.\n\n## Architecture\n\n`KimiTUI` is a **coordinator** that wires state, layout, session, and dialogs together and delegates heavy logic to controllers.\n\n- `src\u002Ftui\u002Fkimi-tui.ts` — the `KimiTUI` coordinator. Holds `state`, owns startup\u002Fshutdown order, layout\u002Feditor wiring, user-input entry, sending\u002Fqueueing, session lifecycle, and the slash-command handler dispatch. It should **not** accumulate event-routing or rendering logic — those live in controllers.\n- `src\u002Ftui\u002Ftui-state.ts` — `TUIState`, `createTUIState`, `createInitialAppState`. The single global UI state shape. Before adding a new global field, decide whether it truly belongs here vs. local component state.\n- `src\u002Ftui\u002Fcontrollers\u002F` — the independently-testable responsibilities. Each controller owns one slice:\n  - `session-event-handler.ts` — routes SDK session events (`handleEvent` dispatch + the per-event `handleXxx`). Concrete event handling goes here, not in `KimiTUI`.\n  - `streaming-ui.ts` — streaming render: assistant delta, thinking, tool call \u002F result, compaction, subagent, background agent, transcript aggregation.\n  - `session-replay.ts` — resume\u002Freplay orchestration; drives replay records through the same live render hooks. Stateless replay parsing\u002Flimiting\u002Fprojection helpers belong in `src\u002Ftui\u002Futils\u002Fmessage-replay.ts`.\n  - `tasks-browser.ts` — the tasks browser controller.\n  - `editor-keyboard.ts` — editor keyboard handling, exit shortcuts, external editor, clipboard image.\n  - `auth-flow.ts` — login\u002Fauth orchestration (`refreshConfigAfterLogin`, etc.).\n- `src\u002Ftui\u002Fcommands\u002F` — slash-command declaration, parsing, ordering, and dynamic skill-command generation. Parsing and types only; execution is dispatched from `KimiTUI`'s slash-command handler section, and complex execution sinks into `utils` or focused components.\n- `src\u002Ftui\u002Fcomponents\u002F` — pi-tui components by UI type: `chrome\u002F` (footer, todo, welcome, loader, device code), `dialogs\u002F` (selectors, approval\u002Fquestion panels, settings popups that replace the editor), `editor\u002F` (input box + mention provider), `media\u002F` (image, diff, code highlight), `markdown\u002F` (the app's Markdown wrapper and mermaid art), `messages\u002F` (transcript blocks + tool-renderers), `panes\u002F` (activity, queue).\n- `src\u002Ftui\u002Freverse-rpc\u002F` — adapts SDK approval\u002Fquestion callbacks into UI panel data and the user's choice back into an SDK response.\n- `src\u002Ftui\u002Ftheme\u002F` — themes, color tokens, style helpers, pi-tui markdown theme, terminal-background detection. The single source of truth for color.\n- `src\u002Ftui\u002Futils\u002F` — TUI-only utilities (need `TUIState` or a component). App-wide, UI-independent helpers go in `src\u002Futils\u002F`.\n\nWhen a controller or `KimiTUI` section keeps growing, split pure functions, state projections, and presentation components into the matching directory rather than expanding the file.\n\n## Where new features go\n\nThe feature type decides the landing spot:\n\n- **CLI arguments** → `src\u002Fcli\u002Fcommands.ts` \u002F `src\u002Fcli\u002Foptions.ts`, passed into the TUI via `src\u002Fcli\u002Frun-shell.ts`. The CLI never operates on the session directly.\n- **CLI subcommands** → `src\u002Fcli\u002Fsub\u002F`, non-interactive only; reach core via `@moonshot-ai\u002Fkimi-code-sdk`.\n- **Slash commands** → declare\u002Fparse\u002Ftype under `src\u002Ftui\u002Fcommands\u002F`; add the execution entry in `KimiTUI`'s slash-command handler section; sink complex logic into `utils` or a focused component.\n- **Skill-derived commands** → hook into `buildSkillSlashCommands` \u002F the skill command map; do not hard-code a single skill.\n- **Transcript message types** → define the shape in `src\u002Ftui\u002Ftypes.ts`, add\u002Fextend a `components\u002Fmessages\u002F` component, register the renderer in the transcript builder.\n- **Tool-result display** → extend `components\u002Fmessages\u002Ftool-renderers\u002Fregistry.ts` and the renderer; do not stack branches inside `ToolCallComponent`.\n- **Popup \u002F selector** → `components\u002Fdialogs\u002F`, mounted via `mountEditorReplacement`; follow [DESIGN.md](.\u002FDESIGN.md). If triggered by an SDK callback, check whether `reverse-rpc\u002F` needs an adapter\u002Fcontroller\u002Fhandler.\n- **SDK event handling** → add the dispatch in `session-event-handler.ts`'s `handleEvent`, then the matching `handleXxx`.\n- **Streaming render** → `controllers\u002Fstreaming-ui.ts`.\n- **Session start \u002F resume behavior** → the session-management section of `KimiTUI`; replay behavior → `controllers\u002Fsession-replay.ts`, reusing live render paths.\n- **Status bar \u002F activity \u002F queue** → `chrome\u002Ffooter`, `panes\u002Factivity`, `panes\u002Fqueue`, and the matching `updateXxx`.\n- **Configuration option** → read\u002Fwrite + schema in `src\u002Ftui\u002Fconfig.ts`, then the settings UI; persist through `saveTuiConfig` (a component never writes the config file itself).\n- **Constants** → shared CLI\u002FTUI non-copy constants in `src\u002Fconstant\u002F`; TUI-only non-copy constants in `src\u002Ftui\u002Fconstant\u002F`. Component-local copy, option labels, help text, dialog titles\u002Ffooters stay next to their component — do not centralize copy into a global module.\n- **General capability** → no TUI-state dependency → `src\u002Futils\u002F`; depends on TUI state or a component → `src\u002Ftui\u002Futils\u002F`.\n\n## Test placement\n\n- Component behavior tests sit next to the component's existing tests (`test\u002Ftui\u002Fcomponents\u002F...`).\n- Command parsing tests → `test\u002Ftui\u002Fcommands\u002F`.\n- reverse-rpc tests → `test\u002Ftui\u002Freverse-rpc\u002F`.\n- Pure utility tests → next to the corresponding utils tests.\n- Do not create a generic `some-feature.test.ts` just to land a small feature; extend the nearest existing test file.\n\n## Theme system mechanics\n\nThemes are managed centrally under `src\u002Ftui\u002Ftheme\u002F`:\n\n- `colors.ts` — semantic tokens: `ColorPalette`, `darkColors`, `lightColors`.\n- `styles.ts` — common chalk helpers built on top of `ColorPalette`.\n- `pi-tui-theme.ts` — the markdown\u002Fpi-tui theme config.\n- `terminal-background.ts` — terminal background detection used by auto resolution.\n- `bundle.ts` — packs `colors`, `styles`, `markdownTheme` into a `KimiTUIThemeBundle`.\n- `index.ts` \u002F `detect.ts` — theme type and auto\u002Fdark\u002Flight resolution.\n\n> **Keep the color-token set in sync.** `ColorPalette` in `colors.ts` is the source of truth for color tokens. When you add, rename, or remove one, update its mirrors in the same change: the custom-theme JSON schema (`apps\u002Fkimi-code\u002Fsrc\u002Ftui\u002Ftheme\u002Ftheme-schema.json`), the token tables in the custom-theme docs (`docs\u002Fen\u002Fcustomization\u002Fthemes.md` and `docs\u002Fzh\u002Fcustomization\u002Fthemes.md`), and the token table in the `custom-theme` built-in skill (`packages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fcustom-theme.md`).\n\nApply \u002F switch flow:\n\n- UI entry: `ThemeSelectorComponent` → `handleThemeCommand` → `applyThemeChoice`.\n- The real apply step is `KimiTUI.applyTheme`: it updates `state.theme`, `state.appState.theme`, and notifies components to refresh their palette.\n- Persist the choice through `saveTuiConfig` — a component must not write the config file itself.\n\n> The **hard color rules** (no chalk named colors, contrast ratios, no module-top-level cached styled functions, add a `ColorPalette` token before inventing a color) are normative and guard-enforced — they live in `apps\u002Fkimi-code\u002FAGENTS.md`. This skill only covers the mechanics.\n\n## Before you submit\n\n- Run lint \u002F format \u002F test on the files you changed.\n- For any dialog\u002Fselector\u002Finput\u002Ftoggle list, walk the self-check list at the end of [DESIGN.md](.\u002FDESIGN.md).\n- Keep `printableChar()` for printable-key comparisons (CI guard) and `chalk.hex(colors.\u003Ctoken>)` for color (CI guard).\n","# Write TUI (apps\u002Fkimi-code)\n\nThe terminal UI lives in `apps\u002Fkimi-code\u002Fsrc\u002Ftui`. Before writing TUI code, read `apps\u002Fkimi-code\u002FAGENTS.md` for the always-on **map, module boundaries, and hard constraints** (printable-key decoding, no chalk named colors, etc.). This skill is the **how-to**: architecture orientation, feature routing, test placement, theme mechanics, and the dialog spec.\n\nFor any list dialog, selector, input box, or status\u002Ftoggle list, the interaction and visual rules are normative — see **[DESIGN.md](.\u002FDESIGN.md)** in this folder and follow its self-check list before submitting.\n\n## Architecture\n\n`KimiTUI` is a **coordinator** that wires state, layout, session, and dialogs together and delegates heavy logic to controllers.\n\n- `src\u002Ftui\u002Fkimi-tui.ts` — the `KimiTUI` coordinator. Holds `state`, owns startup\u002Fshutdown order, layout\u002Feditor wiring, user-input entry, sending\u002Fqueueing, session lifecycle, and the slash-command handler dispatch. It should **not** accumulate event-routing or rendering logic — those live in controllers.\n- `src\u002Ftui\u002Ftui-state.ts` — `TUIState`, `createTUIState`, `createInitialAppState`. The single global UI state shape. Before adding a new global field, decide whether it truly belongs here vs. local component state.\n- `src\u002Ftui\u002Fcontrollers\u002F` — the independently-testable responsibilities. Each controller owns one slice:\n  - `session-event-handler.ts` — routes SDK session events (`handleEvent` dispatch + the per-event `handleXxx`). Concrete event handling goes here, not in `KimiTUI`.\n  - `streaming-ui.ts` — streaming render: assistant delta, thinking, tool call \u002F result, compaction, subagent, background agent, transcript aggregation.\n  - `session-replay.ts` — resume\u002Freplay orchestration; drives replay records through the same live render hooks. Stateless replay parsing\u002Flimiting\u002Fprojection helpers belong in `src\u002Ftui\u002Futils\u002Fmessage-replay.ts`.\n  - `tasks-browser.ts` — the tasks browser controller.\n  - `editor-keyboard.ts` — editor keyboard handling, exit shortcuts, external editor, clipboard image.\n  - `auth-flow.ts` — login\u002Fauth orchestration (`refreshConfigAfterLogin`, etc.).\n- `src\u002Ftui\u002Fcommands\u002F` — slash-command declaration, parsing, ordering, and dynamic skill-command generation. Parsing and types only; execution is dispatched from `KimiTUI`'s slash-command handler section, and complex execution sinks into `utils` or focused components.\n- `src\u002Ftui\u002Fcomponents\u002F` — pi-tui components by UI type: `chrome\u002F` (footer, todo, welcome, loader, device code), `dialogs\u002F` (selectors, approval\u002Fquestion panels, settings popups that replace the editor), `editor\u002F` (input box + mention provider), `media\u002F` (image, diff, code highlight), `markdown\u002F` (the app's Markdown wrapper and mermaid art), `messages\u002F` (transcript blocks + tool-renderers), `panes\u002F` (activity, queue).\n- `src\u002Ftui\u002Freverse-rpc\u002F` — adapts SDK approval\u002Fquestion callbacks into UI panel data and the user's choice back into an SDK response.\n- `src\u002Ftui\u002Ftheme\u002F` — themes, color tokens, style helpers, pi-tui markdown theme, terminal-background detection. The single source of truth for color.\n- `src\u002Ftui\u002Futils\u002F` — TUI-only utilities (need `TUIState` or a component). App-wide, UI-independent helpers go in `src\u002Futils\u002F`.\n\nWhen a controller or `KimiTUI` section keeps growing, split pure functions, state projections, and presentation components into the matching directory rather than expanding the file.\n\n## Where new features go\n\nThe feature type decides the landing spot:\n\n- **CLI arguments** → `src\u002Fcli\u002Fcommands.ts` \u002F `src\u002Fcli\u002Foptions.ts`, passed into the TUI via `src\u002Fcli\u002Frun-shell.ts`. The CLI never operates on the session directly.\n- **CLI subcommands** → `src\u002Fcli\u002Fsub\u002F`, non-interactive only; reach core via `@moonshot-ai\u002Fkimi-code-sdk`.\n- **Slash commands** → declare\u002Fparse\u002Ftype under `src\u002Ftui\u002Fcommands\u002F`; add the execution entry in `KimiTUI`'s slash-command handler section; sink complex logic into `utils` or a focused component.\n- **Skill-derived commands** → hook into `buildSkillSlashCommands` \u002F the skill command map; do not hard-code a single skill.\n- **Transcript message types** → define the shape in `src\u002Ftui\u002Ftypes.ts`, add\u002Fextend a `components\u002Fmessages\u002F` component, register the renderer in the transcript builder.\n- **Tool-result display** → extend `components\u002Fmessages\u002Ftool-renderers\u002Fregistry.ts` and the renderer; do not stack branches inside `ToolCallComponent`.\n- **Popup \u002F selector** → `components\u002Fdialogs\u002F`, mounted via `mountEditorReplacement`; follow [DESIGN.md](.\u002FDESIGN.md). If triggered by an SDK callback, check whether `reverse-rpc\u002F` needs an adapter\u002Fcontroller\u002Fhandler.\n- **SDK event handling** → add the dispatch in `session-event-handler.ts`'s `handleEvent`, then the matching `handleXxx`.\n- **Streaming render** → `controllers\u002Fstreaming-ui.ts`.\n- **Session start \u002F resume behavior** → the session-management section of `KimiTUI`; replay behavior → `controllers\u002Fsession-replay.ts`, reusing live render paths.\n- **Status bar \u002F activity \u002F queue** → `chrome\u002Ffooter`, `panes\u002Factivity`, `panes\u002Fqueue`, and the matching `updateXxx`.\n- **Configuration option** → read\u002Fwrite + schema in `src\u002Ftui\u002Fconfig.ts`, then the settings UI; persist through `saveTuiConfig` (a component never writes the config file itself).\n- **Constants** → shared CLI\u002FTUI non-copy constants in `src\u002Fconstant\u002F`; TUI-only non-copy constants in `src\u002Ftui\u002Fconstant\u002F`. Component-local copy, option labels, help text, dialog titles\u002Ffooters stay next to their component — do not centralize copy into a global module.\n- **General capability** → no TUI-state dependency → `src\u002Futils\u002F`; depends on TUI state or a component → `src\u002Ftui\u002Futils\u002F`.\n\n## Test placement\n\n- Component behavior tests sit next to the component's existing tests (`test\u002Ftui\u002Fcomponents\u002F...`).\n- Command parsing tests → `test\u002Ftui\u002Fcommands\u002F`.\n- reverse-rpc tests → `test\u002Ftui\u002Freverse-rpc\u002F`.\n- Pure utility tests → next to the corresponding utils tests.\n- Do not create a generic `some-feature.test.ts` just to land a small feature; extend the nearest existing test file.\n\n## Theme system mechanics\n\nThemes are managed centrally under `src\u002Ftui\u002Ftheme\u002F`:\n\n- `colors.ts` — semantic tokens: `ColorPalette`, `darkColors`, `lightColors`.\n- `styles.ts` — common chalk helpers built on top of `ColorPalette`.\n- `pi-tui-theme.ts` — the markdown\u002Fpi-tui theme config.\n- `terminal-background.ts` — terminal background detection used by auto resolution.\n- `bundle.ts` — packs `colors`, `styles`, `markdownTheme` into a `KimiTUIThemeBundle`.\n- `index.ts` \u002F `detect.ts` — theme type and auto\u002Fdark\u002Flight resolution.\n\n> **Keep the color-token set in sync.** `ColorPalette` in `colors.ts` is the source of truth for color tokens. When you add, rename, or remove one, update its mirrors in the same change: the custom-theme JSON schema (`apps\u002Fkimi-code\u002Fsrc\u002Ftui\u002Ftheme\u002Ftheme-schema.json`), the token tables in the custom-theme docs (`docs\u002Fen\u002Fcustomization\u002Fthemes.md` and `docs\u002Fzh\u002Fcustomization\u002Fthemes.md`), and the token table in the `custom-theme` built-in skill (`packages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fcustom-theme.md`).\n\nApply \u002F switch flow:\n\n- UI entry: `ThemeSelectorComponent` → `handleThemeCommand` → `applyThemeChoice`.\n- The real apply step is `KimiTUI.applyTheme`: it updates `state.theme`, `state.appState.theme`, and notifies components to refresh their palette.\n- Persist the choice through `saveTuiConfig` — a component must not write the config file itself.\n\n> The **hard color rules** (no chalk named colors, contrast ratios, no module-top-level cached styled functions, add a `ColorPalette` token before inventing a color) are normative and guard-enforced — they live in `apps\u002Fkimi-code\u002FAGENTS.md`. This skill only covers the mechanics.\n\n## Before you submit\n\n- Run lint \u002F format \u002F test on the files you changed.\n- For any dialog\u002Fselector\u002Finput\u002Ftoggle list, walk the self-check list at the end of [DESIGN.md](.\u002FDESIGN.md).\n- Keep `printableChar()` for printable-key comparisons (CI guard) and `chalk.hex(colors.\u003Ctoken>)` for color (CI guard).\n",{"name":5,"description":7},"main","a6579b95265f20c06d3ff66c116f57b33749c044",".agents\u002Fskills\u002Fwrite-tui",0,"https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO","hypoxanthine.cn","An Undergraduate of Shanghaitech University, interedted in NeRF and related MicroArchitecture.","2026-10-27 12:12:49",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add HypoxanthineOvO\u002FVSPi --skill write-tui",{"tool":39,"command":40},"bunx","bunx skills add HypoxanthineOvO\u002FVSPi --skill write-tui",{"tool":42,"command":43},"pnpm","pnpm dlx skills add HypoxanthineOvO\u002FVSPi --skill write-tui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-tui\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"DESIGN.md","REFERENCE","参考文档",12370,"https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-tui\u002FDESIGN.md",[54,61,68,75,81,88],{"skillNo":55,"name":56,"nameZh":6,"description":57,"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},"01M7ARAVE49M92BFQ1W9EYX9M9","kimi-webbridge","Kimi Browser Extension（Kimi 浏览器扩展，原 Kimi WebBridge）lets AI control the user's real browser — navigate, click, type, read, screenshot, and interact with any website using the user's actual login sessions. Use this skill whenever the user wants to interact with websites, automate browser tasks, scrape web content, or perform any action requiring a real browser. Also use when the user mentions \"browser\", \"webpage\", \"open URL\", \"screenshot\", or asks to read\u002Finteract with any website. Use even for simple-sounding browser requests — the daemon handles all complexity.","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fkimi-webbridge\u002Fskills\u002Fkimi-webbridge\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},"01M7ARAMV3ZJXR9H31TPTFEH48","kimi-datasource","Universal data-source assistant for stocks (Wind, S&P, SEC EDGAR), macro (World Bank, IMF, FRED, NBS), Chinese government data and standards (GB\u002FHB\u002FDB\u002FTT), corporate, academic, legal, WHO\u002FFAO\u002FOECD and other IGO data, financial news (Xinhua, Caixin).\nThis plugin exposes tools via MCP server `plugin-kimi-datasource_data`; call them in the flow `mcp__plugin-kimi-datasource_data__get_data_source_desc` → `mcp__plugin-kimi-datasource_data__call_data_source_tool`.","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fkimi-datasource\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},"01M7ARAKQ8P8CKK746J5HJ9495","golden-skill","Golden fixture skill","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002Fpackages\u002Fmigration-legacy\u002Ftest\u002Ffixtures\u002Fgolden\u002F.kimi\u002Fskills\u002Fgolden-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"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":78,"categories":79,"keywords":80,"publishedAt":19},"01M7ARAJTGVPB8C952VSW8XGS3","tools","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Ftools\u002Fskill.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7ARAGJQ99R06PFPPFBC4D0J","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\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Freview\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7ARADHK3K6D34SX07A36XVZ","consolidate","Apply an approved sub-skill grouping by moving user-specified skills into a parent bundle, with timestamped backups of every modified directory.","https:\u002F\u002Fgithub.com\u002FHypoxanthineOvO\u002FVSPi\u002Fblob\u002Fmain\u002Fpackages\u002Fagent-core-v2\u002Fsrc\u002Ffeatures\u002Fskill\u002Fcatalog\u002Fbuiltin\u002Fsub-skill\u002Fconsolidate\u002FSKILL.md",[],[]]