copilot-delegate
Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself.
Install / Use
npx skills add amElnagdy/delegate-skills --skill copilot-delegateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of copilot-delegate
copilot-delegate scores 89/100 on our quality scale, 1600th of 4,698 Development & Engineering skills we index (top 35%).
Its SKILL.md is 7.0 KB long, well organised into 21 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 copilot-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.
copilot-delegate compared with similar skills
All 4 of these similar skills score higher than copilot-delegate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| copilot-delegate (this skill)by amElnagdy | 89 | 2.2k | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 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 |
Frequently asked questions
- How do I install copilot-delegate?
- Run
npx skills add amElnagdy/delegate-skills --skill copilot-delegate. The install tabs above show the steps for each supported agent. - Which AI agents does copilot-delegate work with?
- It is written for GitHub Copilot, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is copilot-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 copilot-delegate still maintained?
- The repository was last updated about 2 months ago, so copilot-delegate is actively maintained.
Skill content
View source on GitHubname: copilot-delegate
description: >-
Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then
review its diff and land it yourself. Use this whenever the user wants to delegate implementation
work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it
through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of
coding tasks through Copilot 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
compatibility: Requires the copilot CLI installed and authenticated (copilot login), Node 18+ to run the relay (the copilot CLI itself requires Node 22+), and git. The orchestrator must be able to run shell commands and read files.
metadata:
version: 0.5.0
Copilot Delegate
You are the orchestrator. Delegate a bounded coding task to a separate implementer — the GitHub Copilot CLI — then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own session in a clean working tree; 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
copilotCLI is not installed or authenticated. - You need a hard sandbox. Copilot exposes sandbox controls, but they are upstream-experimental
(MXC-based, controlled via the
/sandboxcommand and settings, disabled by default) — this relay does not configure them.--read-onlyonly disables edit tools (--mode plan); shell commands still run. If project files must not change at all, dispatch against a clean or isolated worktree.
Prerequisites (check once)
- Install
copilot(npm install -g @github/copilot; the CLI requires Node 22+, the relay itself runs on Node 18+ — the relay probescopilot version). - Authenticate: run
copilot login(interactive web/device flow), or setCOPILOT_GITHUB_TOKEN/GH_TOKEN/GITHUB_TOKENin the environment. - Confirm
copilot versionsucceeds. - Work in, or point
--cdat, the target git repository.
Choose the model (optional)
Copilot picks a default model (auto). To choose another, pass --model <name>.
The relay accepts letters, digits, and . _ : / - only (the value reaches a shell on Windows).
Choose the effort (optional)
Copilot supports a reasoning effort dial: --effort <level> with values
low, medium, high, xhigh, or max. The relay rejects any other value
before dispatch.
The loop
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
1. Write a brief
Copilot sees only the text you send. It cannot read your conversation: the brief must stand alone
with the goal, current state, what to change, what to leave untouched, the project's real
gates, and a report contract. Keep each brief to a single task. Write it to a file and pass it as
the relay's --brief. See references/writing-the-brief.md.
2. Dispatch
Use the bundled relay. It runs copilot -p with --output-format json --no-color --stream off,
captures the JSONL event stream, and writes result.json.
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# choose a model: add --model <name>
# set reasoning effort: add --effort <level>
# read-only planning pass: add --read-only (forces --mode plan)
# full tool autonomy: add --allow-all-tools
# hard time limit (watchdog): add --timeout 2h (the 30m default suits brief runs)
# resume a session: add --session <id> or --resume-last
# see all options: node .../relay.mjs --help
The child's cwd pins the workspace. 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 relay blocks until copilot 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 copilot exits 127 and writes status: "copilot_unavailable".
Completion means the process exited and result.json exists — trust process state and the
working tree, not the progress display. Copilot's final assistant message is the finalMessage
field of result.json.
4. Review — do not trust the self-report
- Re-run the project's gates yourself.
- Read the diff against the brief, starting with
touchedFiles. - Run relevant guard skills if installed.
See references/review-and-land.md.
5. Land it
If the work is good, commit it. The relay never commits — the diff and result.json are the
record; run git status and git diff first to confirm exactly what changed. If the group has a
PR flow, make the commit and push a branch; let human review happen. If the diff is wrong or
incomplete, re-dispatch a corrected brief in a fresh run and review again.
Autonomy and permissions
Without --allow-all-tools, copilot auto-denies tool calls in headless mode: the process exits 0
but the relay detects the denial events and reports status: "failed" with the CLI's own error
message and a hint to pass --allow-all-tools. This is the honest default — the orchestrator sees
the failure rather than a silent no-op.
--allow-all-tools explicitly grants full tool autonomy. --read-only selects --mode plan,
which disables edit tools so project files can't be changed by direct edits; it works without
--allow-all-tools. Shell commands still run in plan mode, so it guards against edits, not
against everything. The two flags are mutually exclusive.
Copilot also exposes sandbox controls, but they are upstream-experimental (MXC-based, controlled
via the /sandbox command and settings, disabled by default). This relay does not configure them.
Authorization model
Delegation is something the human opts into. Once briefed, copilot works as a tool you approved use of. The boundary is: do not accept conclusions from the self-report; verify everything on disk. For anything touching credentials, production data, or irreversible operations, stop and ask the human first instead of encoding it in a brief.
References
- references/writing-the-brief.md — structure, scope, gates, brief delivery.
- references/dispatch-and-poll.md — flags, artifacts,
result.json, and failure recovery. - references/review-and-land.md — what to verify before calling the diff done, at the end of a run.
- 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
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
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.
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.
