Kimi CLI 无法递归加载嵌套 skill 目录（如 .agents/skills/{name}/skills/xxx），Codex 兼容而 Kimi 不兼容 || Kimi CLI cannot recursively load nested skill directories (such as .agents/skills/{name}/skills/xxx), Codex is compatible but Kimi is not

[retamia]

What feature would you like to see?

问题描述

Kimi CLI 目前不支持递归加载嵌套 skill 目录，而 Codex 支持。
这导致同一个仓库中，Codex 能识别并使用 .agents/skills/cloudlive/skills/cloudlive-project-layout 这类嵌套 skill，但 Kimi CLI 无法发现它们。

实际案例

在 cloudlive 仓库中，存在如下嵌套 skill 结构：
.agents/skills/cloudlive/
└── skills/
├── cloudlive-project-layout/SKILL.md
├── cloudlive-repository-model/SKILL.md
└── cloudlive-testing/SKILL.md

• Codex：可以正常加载并提示使用 $cloudlive-project-layout 等 skill。
• Kimi CLI：启动时只扫描 .kimi/skills/ 或 .agents/skills/ 的直接子目录，不会递归进入下一级 skills/ 目录，因此上述 skill 在 Kimi 中完全不可见。

影响

1. 团队需要为 Codex 和 Kimi 维护两套 skill 目录结构，增加维护成本。
2. 现有按模块/项目分组的嵌套 skill 组织方式（如 cc-skills-golang 也使用了 skills/ 子目录）无法平滑迁移到 Kimi。
3. AGENTS.md 中引用的 skill 名称在 Kimi 会话中失效，降低了开发体验一致性。

期望行为

Kimi CLI 能够像 Codex 一样，递归扫描 .kimi/skills/ 和 .agents/skills/ 目录下的所有子目录，只要找到包含 SKILL.md 的目录即识别为一个可用 skill。

环境信息

• Kimi CLI 版本：最新版
• 操作系统：macOS
• 仓库路径示例：.agents/skills/cloudlive/skills/cloudlive-project-layout

Additional information

No response

---

What feature would you like to see?

Problem description

Kimi CLI currently does not support recursive loading of nested skill directories, while Codex does.
This results in that in the same warehouse, Codex can recognize and use nested skills such as .agents/skills/cloudlive/skills/cloudlive-project-layout, but Kimi CLI cannot discover them.

Actual case

In the cloudlive warehouse, there is the following nested skill structure:
.agents/skills/cloudlive/
└── skills/
├── cloudlive-project-layout/SKILL.md
├── cloudlive-repository-model/SKILL.md
└── cloudlive-testing/SKILL.md

• Codex: Can be loaded normally and prompted to use skills such as $cloudlive-project-layout.
• Kimi CLI: Only scan the direct subdirectories of .kimi/skills/ or .agents/skills/ when starting, and will not recurse into the next level skills/ directory, so the above skills are completely invisible in Kimi.

Impact

1. The team needs to maintain two sets of skill directory structures for Codex and Kimi, which increases maintenance costs.
2. The existing nested skill organization method grouped by modules/projects (such as cc-skills-golang also uses the skills/ subdirectory) cannot be smoothly migrated to Kimi.
3. The skill name referenced in AGENTS.md is invalid in the Kimi session, reducing the consistency of the development experience.

Desired behavior

Kimi CLI can, like Codex, recursively scan all subdirectories under the .kimi/skills/ and .agents/skills/ directories. As long as the directory containing SKILL.md is found, it will be recognized as an available skill.

Environment information

• Kimi CLI version: latest version
• Operating system: macOS
• Warehouse path example: .agents/skills/cloudlive/skills/cloudlive-project-layout

Additional information

No response