Kimi Delegate
Delegate a coding task to the Kimi Code CLI (`kimi`) as a background implementer, then...
Install
npx skills add amElnagdy/delegate-skills --skill kimi-delegate -g -a claude-code -y- Repository
- amElnagdy/delegate-skills2.5k
- Category
- Engineering
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,589 tokens
- Runs scripts
- Yes, review before use
What it does
Delegate a coding task to the Kimi Code CLI (`kimi`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Kimi - phrasings like "have Kimi implement X", "delegate this to Kimi", "run it through Kimi Code", or "use Kimi to implement/fix/refactor" - or wants to run a queue of coding tasks through Kimi while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
Kimi Delegate
You are the orchestrator. Hand a bounded coding task to a separate implementer - the Kimi Code CLI - then review what it produced and land it yourself. You write the brief and own the judgment; Kimi does the typing in its own session; you verify and commit.
The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
When NOT to use this
- The task is small enough to do inline; delegation overhead is not worth it.
- The
kimiCLI is not installed or authenticated. - You need a CLI-enforced read-only implementer. Headless Kimi has no read-only mode.
Prerequisites (check once)
- Install Kimi Code with
brew install kimi-codeon macOS/Linux, or use the native installer from the official Kimi Code documentation. - Authenticate with
kimi login(device-code flow, no TUI), or use/loginin the TUI. - Confirm
kimi --versionsucceeds. - Work in, or point
--cdat, the target git repository.
Choose the model alias
Kimi uses default_model from its config.toml when --model is omitted. To choose another model
alias, pass --model <alias from your kimi config>. Model aliases are user-defined config keys; use
one the human has configured rather than inventing one.
The loop
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
1. Write the brief
Kimi sees only the text you send plus what it can inspect in the workspace - no chat history or shared context. Include the goal, current state, what to change, what to leave untouched, the project's actual gates, and a report contract. Tell Kimi not to commit. Keep one task per brief. See references/writing-the-brief.md.
