📦amElnagdy / delegate-skills
← 返回首页
Delegate a coding task to a separate coding agent CLI, review the diff, land the commit yourself — one per implementer.
⚖️ MIT#agent-skills#claude-code#coding-agent#openai-codex#ai-coding-agent🌐 www.skills.sh📅 创建于 2026-06-14🔄 更新于 2026-10-14
🔗 GitHub JavaScript

📄 仓库 README

在 GitHub 查看 ↗
来自 GitHub 仓库自述文件 · 版权归原作者所有

delegate-skills

relay smoke skills.sh License

Create your fleet of lanes. One orchestrator, the right implementer for every job.

Discover the implementer CLIs already installed on your machine, organize them into lanes like feature, tests, and ui, then delegate by lane — or choose one implementer directly. Either way, you keep the review and the commit.

npx skills add amElnagdy/delegate-skills

Then ask your orchestrating agent to create the fleet:

Use $delegate-setup to discover my installed implementer CLIs and create a fleet for feature, tests, and UI work.

Or delegate directly:

Use $codex-delegate to have Codex implement the refactor in services/billing/, then review and commit it.

flowchart LR
  S["$delegate-setup<br/>discover → propose → approve"] --> F["Example fleet"]
  O["Your orchestrator"] --> F
  F -->|"feature"| A["OpenCode"]
  F -->|"tests"| B["Codex"]
  F -->|"ui"| C["Cursor"]
  A --> R["Review the diff<br/>Run the gates"]
  B --> R
  C --> R
  R --> L["You land the commit"]

Choose how you delegate

Create a fleet

Skill Job
delegate-setup Discover installed CLIs, propose fleet lanes, and write global or project config after you approve. Never dispatches work.

A fleet is your set of named lanes. Each lane binds a kind of work to one implementer and optional dials such as model, effort, or variant. Setup discovers what is available, proposes a compact fleet, shows you the complete configuration, and writes only after explicit approval.

Configuration can apply globally or to one repository. Once it is ready, dispatch with the matching *-delegate skill and --lane <name>. Explicit flags override lane dials, and the wrong implementer skill for a lane fails loud. Project config is content-bound to explicit setup approval, so cloned or edited project lanes fail closed until re-approved. See the delegate-fleet.v1 schema for paths, supported dials, and overlay behavior.

Delegate directly

Skip setup when you want one implementer or one-off dials. Pick the skill for a CLI you have:

Skill Implementer CLI Write access (default) Read-only run Resume
aider-delegate Aider (aider) — any OpenAI-compatible endpoint, including a local or self-hosted model via --api-base --yes-always with --no-suggest-shell-commands; no sandbox or permission modes; commits force-disabled 3 --read-only (--dry-run) --resume-last (chat history, per-worktree)
agy-delegate Google Antigravity (agy) Antigravity's own permissions; bypass opt-in --read-only (plan mode) --resume-last, --conversation <id>
claude-delegate Claude Code (claude) acceptEdits + explicit tool surface --read-only (plan mode) --resume-last, --session <id>
cline-delegate Cline (cline) --auto-approve true in act mode; upstream sandbox not configured by the relay --plan + --auto-approve false (relay-enforced pair) — (headless JSON resume unsupported)
codex-delegate OpenAI Codex (codex) --sandbox workspace-write --read-only --resume-last, --session <id>
commandcode-delegate Command Code (cmd; cmdc on Windows) --yolo — the only headless write state; no sandbox 1 --read-only (withheld tools + plan) --continue-last, --session <id>
cursor-delegate Cursor Agent (cursor-agent) --force; --no-force withholds command approval --read-only (plan mode) --resume-last, --session <id>
grok-delegate Grok Build (grok) workspace-scoped; --full-access opt-in --read-only — best-effort 4 --resume-last, --session <id>
kimi-delegate Kimi Code (kimi) auto permission mode, always — 2 --resume-last, --session <id>
muse-delegate Muse Code (muse) --disable-approval (sandbox on); not --yolo 5 --read-only (--disable-write + --disable-shell) --session <id> (no headless --resume-last)
opencode-delegate OpenCode (opencode) agent build (--model required) --read-only (agent plan) --resume-last, --session <id>
pi-delegate Pi (pi) full local tools — no sandbox, no permission modes 2; project trust opt-in --read-only (read,grep,find,ls) --resume-last, --session <id>
omp-delegate Oh My Pi (omp) --yolo (tools.approvalMode: yolo); project .omp extras off unless --approve --read-only (read,grep,glob) --resume-last, --session <id>
qoder-delegate Qoder (qodercli) auto permission mode; bypass opt-in --permission-mode plan --resume-last, --resume <id>
vibe-delegate Mistral Vibe (vibe) accept-edits; --full-access opt-in --plan-only (plan agent) --resume-last, --session <id>
copilot-delegate GitHub Copilot CLI (copilot) --allow-all-tools opt-in; headless auto-deny otherwise --read-only (--mode plan) --resume-last, --session <id>
warp-delegate Warp Agent CLI (oz) full local tools — no sandbox, no permission modes 2 — 2 --conversation <id>
zcode-delegate Z.AI ZCode (zcode) 6 --mode yolo --read-only (plan mode) --resume-last, --session <id>

Each skill name links to its SKILL.md, which owns that implementer's prerequisites, flags, and caveats. Building one for another CLI? [Claim it first](https://github.com/amEln

  1. Command Code's headless mode has two states and nothing between them: a -p run withholds the write, edit, and shell tools, and --yolo (alias --dangerously-skip-permissions) allows every tool anywhere the process can reach. --permission-mode auto-accept and --tools-all do not lift the write gate. So an implementation run is full-trust with no path restriction — the brief's path list is guidance, not containment. A worktree isolates the checkout, while a container or another OS-enforced sandbox is required when writes outside the target tree are unacceptable. touchedFiles is a review aid based on git status; it cannot show ignored files or writes outside the repository. ↩

  2. No CLI-enforced read-only mode. touchedFiles and the diff are what you review against, not a guarantee: they are post-run git status in the workspace, so they cannot show ignored files, reverted edits, or writes outside the repository. ↩↩↩↩

  3. Aider is the one implementer here that commits by default. Its --auto-commits and --dirty-commits both default to True, the second of which commits your pre-existing uncommitted work before editing. The relay always passes --no-auto-commits and --no-dirty-commits, and neither is configurable through it. ↩

  4. grok cannot be prevented from writing headlessly. The relay reports a tri-state readOnlyViolation tripwire for detected Git-visible changes; it does not enforce or attribute them. ↩

  5. Write muse exec keeps Muse's sandbox on and passes --disable-approval so a headless run cannot hang on a tool-approval prompt. --read-only adds --disable-write and --disable-shell. --yolo is not the default and is not exposed. Upstream's launcher is Darwin/Linux only. Headless resume is --session-id; muse resume is TUI-only. ↩

  6. ZCode ships its CLI inside the desktop app — there is no zcode on PATH, no npm package, and the public docs cover only the GUI. The relay resolves it from --zcode-path/ZCODE_CLI, then PATH, then the installed app bundle. Of ZCode's four documented modes only plan and yolo work headlessly: build and edit have no permission client there, so they block every write tool and exit 0 having changed nothing, and the relay rejects them rather than report that as success. ZCode offers --disallowed-tools but no --allowed-tools, so capability can be subtracted, never enumerated. Where zcode login fails with OAuth response is not valid JSON, the key comes from ZCODE_API_KEY / ANTHROPIC_API_KEY / ZAI_API_KEY instead. ↩

📈 近 7 天 Star 趋势

每日新增 Star（柱）与累计 Star（线）· 数据来自 GitHub

🏆 排名变化趋势

在各榜单中的排名历史（数字越小越靠前）

📋 历史上榜记录

每次快照的详细数据
日期 榜单 排名 周期新增 总 STAR