MoonshotAI / MoonshotAI/kimi-code

Feature: runtime skill source toggles and per-name skill exclusion

Open
#2,549 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

What feature would you like to see?

Motivation

Currently, all six skill sources (builtin, user, workspace, plugin, extra, explicit) are unconditionally merged into the skill catalog, and every discovered skill appears regardless of user preference. There is no way to:

  • Disable an entire skill source at runtime (e.g. suppress workspace skills in favor of a curated builtin set).
  • Hide specific skills by name without removing them from disk.

Proposed solution

Two new config.toml sections consumed by WorkspaceSkillCatalogService:

[skill_sources]

Per-source boolean toggles. Setting any key to false disables that entire source in the merged catalog. The source is still scanned; only the merge phase skips it.

[skill_sources]
workspace = false   # hide project-level skills
plugin = false      # hide plugin-contributed skills

All six sources default to enabled when the key is absent or the entire section is omitted.

exclude_skill_names

A string array of skill names to exclude from the merged view, compared case-insensitively.

exclude_skill_names = ["git-commit-message-zh", "map-game-codebase-zh"]

Default is [] (no exclusion).

Scope

agent-core-v2 only — consumed by WorkspaceSkillCatalogService.remerge(). Config changes take effect immediately without requiring a restart.

Branch

Implementation ready at feat/skill-source-toggles

Additional information

No response

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 with WorkspaceSkillCatalogService.remerge() and the config.toml handling in agent-core-v2; trace how the six sources are merged and how runtime config changes are observed. Check the implementation branch and existing catalog/config tests, then verify disabled sources, case-insensitive name exclusions, defaults, and immediate remerge behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.