Skip to content

feat(cli): add built-in kilo-config skill - #7603

Merged
alex-alecu merged 6 commits into
mainfrom
feat/builtin-config-skill
Mar 27, 2026
Merged

feat(cli): add built-in kilo-config skill#7603
alex-alecu merged 6 commits into
mainfrom
feat/builtin-config-skill

Conversation

@alex-alecu

@alex-alecu alex-alecu commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

Followup to #7573

Why

When users ask about configuring Kilo, the agent has to fetch docs from the web, which is slow and unreliable. We need the configuration reference available instantly without burning system prompt tokens on every request.

Additionally, users asking the agent to change TUI settings (e.g. "toggle dark mode", "switch theme") got incorrect answers because the agent had no knowledge of the ctrl+p command palette, keybinds, or slash commands.

What changed

Added a built-in skill called kilo-config that ships inside the CLI binary. It contains a dense reference covering all configuration surfaces: commands, agents, permissions, MCP servers, providers, skills, plugins, and every kilo.json field. The skill is registered at the lowest precedence before all filesystem discovery, so any user-defined skill with the same name cleanly overrides it. The skill tool now handles built-in skills without trying to list files or resolve filesystem paths. The cost is about 60 tokens per request for the skill listing, with the full ~1,500 token reference loaded on-demand only when relevant.

The skill now also includes a TUI Settings section documenting all ctrl+p command palette actions, keybinds, and slash commands — covering themes, dark/light appearance toggle, session management, agent/model switching, and display toggles. The skill description was widened so the agent loads it when users ask about changing settings or appearance, not just kilo.json config. The section explicitly notes that these are user-interactive only and the agent should direct users to the right command rather than trying to change settings itself.

Demo

Look for Skill "kilo-config":

Screenshot 2026-03-27 at 10 14 19

When asking for things that CLI cannot control yet:

Screenshot 2026-03-27 at 10 59 31

How to test

  1. Run bun run typecheck from packages/opencode/ — should pass clean
  2. Start the CLI and ask "how do I configure permissions in kilo?" — the agent should load the kilo-config skill instead of fetching web docs
  3. Ask "can you toggle dark mode?" — the agent should load the skill and direct you to Ctrl+P → "Toggle appearance" instead of suggesting terminal settings

Comment thread packages/opencode/src/skill/skill.ts
Comment thread packages/opencode/src/kilocode/skills/kilo-config.md Outdated
@kilo-code-bot

kilo-code-bot Bot commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • packages/opencode/src/kilocode/skills/builtin.ts
  • packages/opencode/src/kilocode/skills/kilo-config.md

Reviewed by gpt-5.4-20260305 · 983,421 tokens

Comment thread packages/opencode/src/skill/skill.ts
@alex-alecu alex-alecu self-assigned this Mar 27, 2026
The agent had no knowledge of ctrl+p commands, themes, or appearance
toggling, so it told users to change their terminal settings instead.
Add a TUI Settings section covering all command palette actions,
keybinds, and slash commands, and widen the skill description to
trigger on settings/appearance questions.
@alex-alecu
alex-alecu merged commit 536f7f9 into main Mar 27, 2026
22 checks passed
@alex-alecu
alex-alecu deleted the feat/builtin-config-skill branch March 27, 2026 09:45
slamj1 pushed a commit to slamj1/kilocode that referenced this pull request May 16, 2026
jliounis pushed a commit to jliounis/kilocode that referenced this pull request May 18, 2026
jliounis pushed a commit to jliounis/kilocode that referenced this pull request May 18, 2026
t7tran pushed a commit to t7tran/kilocode that referenced this pull request Aug 14, 2026
t7tran pushed a commit to t7tran/kilocode that referenced this pull request Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants