fix(cli): restore built-in skill registration

[alex-alecu]

Why

The kilo-config built-in skill stopped loading after the upstream OpenCode v1.3.5 merge (6cf72ef). The Effect migration in that commit refactored the skill service internals, and the Kilo-specific loop that seeded built-in skills into state was not preserved. Users asking about Kilo configuration no longer got the skill that teaches the agent how Kilo settings work.

What changed

Re-added the registration loop that seeds built-in skills into the skill service before filesystem discovery runs. The import and constants were already in place — only the loop that actually writes them into state was missing. Built-in skills are registered first so that any user-created skill with the same name naturally takes priority. Existing tests were updated to filter out built-in skills when counting filesystem-discovered skills, making them resilient to future built-in additions. A new regression test verifies built-in skills load correctly and can be overridden.

How to test

Start the CLI bun dev, open a session, and ask "how do I configure Kilo?" — the agent should use the kilo-config skill.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (4 files)

• packages/kilo-vscode/webview-ui/src/components/settings/AgentBehaviourTab.tsx
• packages/opencode/src/skill/index.ts
• packages/opencode/test/kilocode/builtin-skills.test.ts
• packages/opencode/test/skill/skill.test.ts

---

_{Reviewed by gpt-5.4-2026-03-05 · 351,503 tokens}