kimi-delegate
Delegate a coding task to the Kimi Code CLI (`kimi`) as a background implementer, then review its diff and land it yourself.
Install / Use
npx skills add amElnagdy/delegate-skills --skill kimi-delegateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of kimi-delegate
kimi-delegate scores 89/100 on our quality scale, 1603rd of 4,698 Development & Engineering skills we index (top 35%).
Its SKILL.md is 6.1 KB long, well organised into 18 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,181 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so kimi-delegate is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
kimi-delegate compared with similar skills
All 4 of these similar skills score higher than kimi-delegate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| kimi-delegate (this skill)by amElnagdy | 89 | 2.2k | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install kimi-delegate?
- Run
npx skills add amElnagdy/delegate-skills --skill kimi-delegate. The install tabs above show the steps for each supported agent. - Which AI agents does kimi-delegate work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is kimi-delegate safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is kimi-delegate still maintained?
- The repository was last updated about 2 months ago, so kimi-delegate is actively maintained.
Skill content
View source on GitHubname: 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
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.
2. Dispatch
Use the bundled helper. It wraps Kimi's headless prompt mode, captures the structured event stream,
and writes result.json. (<skill-dir> is the installed folder containing this SKILL.md.)
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
The child process's cwd pins the workspace. Use repeatable --add-dir flags only for extra workspace
directories. The relay writes artifacts under the system temp dir by default and never commits. See
references/dispatch-and-poll.md.
3. Wait for completion
The helper blocks until Kimi finishes. Run it with the orchestrator's background-command facility, or
background it in the shell and poll for result.json. A pre-run usage error exits 2 and writes no
result; a missing kimi exits 127 and writes status: "kimi_unavailable".
Trust process state and the working tree over a progress display. Completion means the process exited
and result.json exists. Kimi's full report is the finalMessage field in result.json (also printed
in full on stdout between the report markers).
4. Review - do not trust the self-report
Treat Kimi's final message and gate claims as claims:
- Re-run the project's gates yourself.
- Read the diff against the brief, starting with
touchedFiles. - Run relevant guard skills if installed.
- Round-trip migrations and grep for dangling references after removals or renames.
See references/review-and-land.md.
5. Land it
The implementer edits the working tree; the orchestrator commits. Commit only after the gates pass
and the diff holds. If rework is needed, send a delta brief with --resume-last or --session <id>,
then review again.
Autonomy and permissions
In headless -p mode, Kimi always runs in auto permission mode and never asks for approval. Kimi
rejects --prompt combined with --yolo, --auto, or --plan, so the relay passes none of them and
offers no --read-only or --full-access option. There is no CLI-enforced read-only mode: inspect
touchedFiles and the diff after every run. That diff, not a flag, is the guarantee of what changed.
Authorization model
Delegation is something the human opts into. Once they have ("run this queue", "proceed"), committing verified, gate-passing work is the agreed contract. Two limits remain: surface, don't absorb (report Kimi's design decisions, defensible-but-unasked turns, and non-blocking nitpicks) and stop for scope changes (if correct completion needs going beyond the brief, ask instead of expanding the mandate). See references/review-and-land.md.
References
- references/writing-the-brief.md - structure, report contract, real gates, argv delivery, and delta briefs.
- references/dispatch-and-poll.md - flags, artifacts,
result.json, polling, and failure recovery. - references/review-and-land.md - review checklist, commit boundary, and rework through Kimi sessions.
- references/multi-task-queues.md - sequential queues, constraint carry-forward, progress tracking, and the final coherence pass.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
