cursor-delegate
Delegate a coding task to the Cursor Agent CLI (`cursor-agent`) as a background implementer, then review its diff and land it yourself.
Install / Use
npx skills add amElnagdy/delegate-skills --skill cursor-delegateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of cursor-delegate
cursor-delegate scores 89/100 on our quality scale, 1601st of 4,700 Development & Engineering skills we index (top 35%).
Its SKILL.md is 8.4 KB long, well organised into 22 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 cursor-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
ReviewOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The relay always passes `--trust` to `cursor-agent`, disabling the workspace-trust prompt for headless runs.
AI review: risky
- The relay always passes `--trust` to `cursor-agent`, disabling the workspace-trust prompt for headless runs.
- A fresh run defaults to write-capable with `--force`, so Cursor runs commands without approval unless explicitly denied in config.
- While the skill has a legitimate delegation purpose, these defaults meaningfully weaken the delegated agent's permission safeguards.
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.
cursor-delegate compared with similar skills
All 4 of these similar skills score higher than cursor-delegate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| cursor-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 cursor-delegate?
- Run
npx skills add amElnagdy/delegate-skills --skill cursor-delegate. The install tabs above show the steps for each supported agent. - Which AI agents does cursor-delegate work with?
- It is written for Cursor, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is cursor-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 judged it risky: The relay always passes
--trusttocursor-agent, disabling the workspace-trust prompt for headless runs. 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 cursor-delegate still maintained?
- The repository was last updated about 2 months ago, so cursor-delegate is actively maintained.
Skill content
View source on GitHubname: cursor-delegate
description: >-
Delegate a coding task to the Cursor Agent CLI (cursor-agent) as a background implementer, then
review its diff and land it yourself. Use this whenever the user wants to hand implementation work
to Cursor — phrasings like "have Cursor implement X", "delegate this to Cursor", "run it through
Cursor Agent", or "use Cursor to implement/fix/refactor" — or wants to run a queue of coding tasks
through Cursor 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 cursor-agent CLI installed and authenticated, Node 18+, and git. The optional --add-dir flag requires cursor-agent 2026.07.23 or newer. The orchestrating agent must be able to run shell commands and read files. Shell examples assume bash/zsh (macOS/Linux, or Git Bash/WSL on Windows).
metadata:
version: 0.5.0
Cursor Delegate
You are the orchestrator. Hand a bounded coding task to a separate implementer — the Cursor Agent CLI — then review what it produced and land it yourself. You write the brief and own the judgment; Cursor 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
cursor-agentCLI is not installed or authenticated (runcursor-agent login). - You want to write the code yourself, or you only need Cursor's opinion on code you wrote (a
--read-onlydispatch covers that — see below — but a plain review may not need delegation at all).
Prerequisites (check once)
cursor-agent --versionsucceeds. If not, follow the installer for your platform at cursor.com/cli, inspect what it will run, and authenticate withcursor-agent login.cursor-agent statusshows you logged in.- You are in (or will point
--cdat) the target git repository. The relay passes--trust, so point it only at repositories you trust.
Choose the model
Omitting --model uses your Cursor default (usually auto — Cursor picks). To pin one, pass
--model <name> with a name from the account's live cursor-agent models output — select from that
list rather than inventing a name. Parameterized forms like <name>[context=1m,effort=high] are
forwarded as-is. The model that actually served the run is recorded as resolvedModel in
result.json.
The loop
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
1. Write the brief
Cursor 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 Cursor not to commit. Keep one task per brief. See references/writing-the-brief.md.
2. Dispatch
Use the bundled helper. It wraps cursor-agent -p, feeds the brief on stdin, 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
# read-only (plan mode — review/diagnosis, no edits): add --read-only
# write-capable without automatic command approval: add --no-force
# explicitly override Cursor's sandbox for this run: add --sandbox enabled|disabled
# pin a model from `cursor-agent models`: add --model <name>
# 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. On Cursor 2026.07.23 or newer, 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 Cursor 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 cursor-agent exits 127 and writes status: "cursor_agent_unavailable".
Trust process state and the working tree over a progress display. Completion means the process exited
and result.json exists. Cursor's full report is the finalMessage field in result.json (also
printed in full on stdout between the report markers).
Windows + hooks caveat: if the user has Cursor hooks configured (~/.cursor/hooks.json, or
Claude Code PreToolUse hooks, which cursor-agent imports), dispatching from a Git Bash (MSYS)
console makes cursor-agent feed PowerShell-syntax hook wrappers to bash, so every command Cursor
tries to run is blocked — edits still land, gates do not run. Dispatch from a PowerShell or cmd
console instead. Details: references/dispatch-and-poll.md.
4. Review — do not trust the self-report
Treat Cursor'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
A fresh run defaults to write-capable with --force: Cursor runs commands without approval
unless your Cursor config explicitly denies them, so ordinary gates (tests, linters, builds) run
headlessly. --no-force keeps the run write-capable but withholds automatic command approval;
commands that require approval are refused because a headless run cannot prompt. --read-only
switches to Cursor's plan mode (read-only analysis, no edits, no --force). The relay always
passes --trust to keep headless runs from stalling on the workspace-trust prompt, which is why
--cd must only ever point at repositories you trust. Pass --sandbox enabled or --sandbox disabled only when you need to override Cursor's sandbox for that dispatch. The requested value is
recorded as sandbox in result.json; it does not claim what Cursor actually applied. The permission
mode Cursor reports is recorded as permissionMode; inspect touchedFiles and the diff after every
run.
Read-only second opinions
--read-only doubles as a clean way to get an adversarial second opinion with no write risk:
dispatch a brief that lists the agreed points, then each contested point with both positions, and ask
Cursor to defend or concede each — deliverable in its final message, touching no files.
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 Cursor'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, 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 Cursor 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.
