Kimi Code skills install to ~/.config/agents/skills via the kimi-cli host id

[delete-cloud]

Summary

kitup 0.1.4's host adapter id kimi-cli is the entry used for Kimi Code (kimi / ~/.kimi-code; alias kimi-code-cli). That is kitup's host id, not a separate product called “Kimi CLI”.

That adapter's userSkillsDirs prefers ~/.config/agents/skills. Kimi Code does not scan that directory, so a successful user-scope install for this host can land where Kimi Code never loads skills.

(The older Moonshot kimi-cli layout under ~/.kimi is a different tool.)

Evidence (Kimi Code 0.41.0)

Kimi Code user skill roots are:

• ~/.agents/skills
• $KIMI_CODE_HOME/skills (default ~/.kimi-code/skills)

It does not read ~/.config/agents/skills. That path is Amp / Replit (kitup's amp / replit hosts).

Current spec/hosts.json for host id kimi-cli:

"userSkillsDirs": [
  "~/.config/agents/skills",
  "~/.agents/skills"
]

Why keeping the Amp path as a fallback is still wrong

kitup's choose_scope_path prefers the first candidate directory that already exists. ~/.config/agents/skills is shared with Amp. On a machine where that directory already exists and ~/.agents/skills does not, a fresh install for this host still goes to the unread Amp path.

Proposed fix

Data-only, per the host-adapter contract:

• userSkillsDirs for host id kimi-cli: ["~/.agents/skills"] only
• Do not keep ~/.config/agents/skills as a secondary path
• Note that Kimi Code also reads $KIMI_CODE_HOME/skills, which kitup cannot express (no env expansion in ~/ paths)

PR: #41