# Kimi Delegate

Delegate a coding task to the Kimi Code CLI (`kimi`) as a background implementer, then...

- Repository: https://github.com/amElnagdy/delegate-skills (2546 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add amElnagdy/delegate-skills --skill kimi-delegate -g -a claude-code -y`
Codex: `npx skills add amElnagdy/delegate-skills --skill kimi-delegate -g -a codex -y`
Cursor: `npx skills add amElnagdy/delegate-skills --skill kimi-delegate -g -a cursor -y`
Gemini CLI: `npx skills add amElnagdy/delegate-skills --skill kimi-delegate -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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 `kimi` CLI is not installed or authenticated.
- You need a CLI-enforced read-only implementer. Headless Kimi has no read-only mode.

## Prerequisites (check once)

1. Install Kimi Code with `brew install kimi-code` on macOS/Linux, or use the native installer from
   the [official Kimi Code documentation](https://moonshotai.github.io/kimi-code/en/).
2. Authenticate with `kimi login` (device-code flow, no TUI), or use `/login` in the TUI.
3. Confirm `kimi --version` succeeds.
4. Work in, or point `--cd` at, 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](references/writing-the-brief.md).

### 2. Dispatch

The rest: https://github.com/amElnagdy/delegate-skills/blob/HEAD/skills/kimi-delegate/SKILL.md