Kimi skills never reach the CLI: wrong install dir, overlay hides skills, project scan is claude-only

see above

Fixed on coder/fork-kimi-skills-never-reach-the-cli-wro-6ce0fa.

Three independent misses, all required for a Kimi skill to reach the CLI:

Wrong install dir — SKILL_DIRS.kimi wrote to ~/.kimi/skills. kimi-cli reads $KIMI_CODE_HOME/skills (default ~/.kimi-code/skills).
Overlay hid skills — the per-thread KIMI_CODE_HOME overlay (Isolate Kimi runs: no cross-project threads, memory, or workspaces #671) linked credentials/plugins but not skills, so even a correct install was invisible at runtime.
Project scan was claude-only — Skills tab listing and / expansion only walked <project>/.claude/skills. Repo skills under .kimi-code/skills, .kimi/skills, .agents/skills, etc. never made the palette.

PROJECT_SKILL_RELS is now shared between listSkills and cliCommands.

Moved back to plan:todo (2026-10-03 board cleanup). The fix described above was made on a fork branch, and most of it never reached main.

Only one piece landed: / expansion on a kimi thread scans <project>/.kimi/skills and .agents/skills.

Still missing on main:

Install to $KIMI_CODE_HOME/skills (default ~/.kimi-code/skills). electron/skills.js:59 still uses ~/.kimi/skills.
Link skills into the per-thread KIMI_CODE_HOME overlay. KIMI_HOME_LINKS at electron/kimi.js:56-65 has no skills entry.
Make the Skills tab project scan cover more than .claude/skills (electron/skills.js:466), including .kimi-code/skills.
cliCommands.js:270 project providers are still ["claude", "grok"].

Landed from Solenta thread "Kimi skills never reach the CLI: wrong install dir, overlay " (PR #1646). Closed on merge.

Navigation Menu