Kimi Delegate

What it does

When your agent uses it

• Wants to hand implementation work to Kimi - phrasings like have Kimi implement X
• Delegate this to Kimi
• Run it through Kimi Code
• Use Kimi to implement/fix/refactor -

Example prompts

• “have Kimi implement X”
• “delegate this to Kimi”
• “run it through Kimi Code”
• “/kimi-delegate”

Requirements

• Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Write the brief
2. 2Dispatch
3. 3Wait for completion
4. 4Review - do not trust the self-report
5. 5Land it

What it can do on your machine

Read from SKILL.md and the folder at commit 8ef0210. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (JavaScript), which the agent can run.

  Shell commands in SKILL.md call:

  • node
  • brew

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • moonshotai.github.io

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Kimi Delegate loads about 1.6k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 678 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~136

When it runs · the whole SKILL.md, loaded when a task matches

~1.6k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~6.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from amElnagdy/delegate-skills at commit 8ef0210, republished under its MIT licence (© amElnagdy). 678 words, ~1,550 tokens.

name

kimi-delegate

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.

license

MIT

metadata.version

0.5.0

node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# choose a configured model alias:       add --model <alias from your kimi config>
# resume the most recent session:        add --resume-last  (delta brief only)
# resume a specific session:             add --session <id> (delta brief only)
# hard time limit (watchdog):            add --timeout 2h  (the 30m default suits short runs; implementation briefs routinely need 1-2h)
# see all options:                       node .../relay.mjs --help

© amElnagdy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/kimi-delegate of amElnagdy/delegate-skills.

• SKILL.md
• references/dispatch-and-poll.md
• references/multi-task-queues.md
• references/review-and-land.md
• references/writing-the-brief.md
• scripts/relay.mjs

Open the folder on GitHubat commit 8ef0210