MoonshotAI / MoonshotAI/kimi-cli

Feature request: align user skills discovery with OpenAI Codex "USER" scope ($HOME/.agents/skills)

Open
#1,684 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

OpenAI Codex defines $HOME/.agents/skills as the standard USER scope for personal skills (docs).

Kimi-cli currently lists ~/.agents/skills in get_user_skills_dir_candidates(), but resolve_skills_roots() stops at the first existing candidate. This means if a user has both ~/.config/agents/skills and ~/.agents/skills, only the former is loaded.

Requested changes:

  1. Load all existing user-scope skill directories instead of just the first one.
  2. Walk up the directory tree for project-level discovery (from work_dir to the Git repo root), matching Codex REPO scope behavior.
  3. (Optional) Add an admin/system scope such as /etc/kimi/skills.

This would improve interoperability for users coming from Codex and make $HOME/.agents/skills work reliably as a personal skills folder.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at get_user_skills_dir_candidates() and resolve_skills_roots(), then trace how work_dir and Git-root discovery are handled. Done means all existing user directories are loaded, project discovery walks from work_dir to the repository root, and any admin scope is treated as optional.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.