Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →amelnagdy/kimi-delegate
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
Passed 16 of 19 test cases with the skill, and 8 of 19 without it.
and 8 more in the full report
10 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to supply a follow-up brief to Kimi for a specific previous session identified by `sess_abc123`. Which flag in `relay.mjs` targets this specific session ID?
| Checked | Without skill | With skill |
|---|---|---|
| Passes --session sess_abc123 to relay.mjs. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
kimi CLI is not installed or authenticated.brew install kimi-code on macOS/Linux, or use the native installer from
the official Kimi Code documentation.kimi login (device-code flow, no TUI), or use /login in the TUI.kimi --version succeeds.--cd at, the target git repository.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.
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
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.
test cases passed, vs 8 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.