Agent skill

Claude Delegate

by amElnagdy in amElnagdy/delegate-skills

Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself.

MITAuto-check passedAgent Workflows

Install Claude Delegate

skills CLI
$ npx skills add amElnagdy/delegate-skills --skill claude-delegate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install amElnagdy/delegate-skills claude-delegate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/amElnagdy/delegate-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/claude-delegate .claude/skills/claude-delegate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
claude-delegate
GitHub stars
2.3k
Token cost
~2.4k tokens
SKILL.md length
1,059 words
Files
6 (incl. scripts, references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself.

  • Works in 5 steps: Write the brief → Dispatch → Wait → …
  • Explicitly asks to delegate implementation to Claude Code
  • SKILL.md covers When not to use this, Prerequisites, The loop and Permission profiles, plus 2 more sections
  • Runs JavaScript scripts from its folder; calls claude, node and git

What it does

Claude Delegate is an agent skill from amElnagdy/delegate-skills. Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the claude CLI — for example, "have another Claude implement this", "delegate this to Claude Code", or "run this queue through a separate Claude session." Do not trigger merely because the current orchestrator is Claude, and do not use when the user asks the…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/dispatch-and-poll.md`, `references/multi-task-queues.md` and `references/review-and-land.md`). Compatibility notes: Requires the claude CLI (Claude Code) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read…

It sits in Agent Workflows. The repository describes itself as: Delegate a coding task to a separate coding agent CLI, review the diff, land the commit yourself — one per implementer. The licence is MIT.

When your agent uses it

  • Explicitly asks to delegate implementation to Claude Code
  • Another Claude session
  • The claude CLI — for example
  • Have another Claude implement this

Example prompts

  • “have another Claude implement this”
  • “delegate this to Claude Code”
  • “run this queue through a separate Claude session.”
  • “/claude-delegate”

Requirements

  • Node.js
  • Compatibility (from SKILL.md): Requires the `claude` CLI (Claude Code) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Claude's shell sandbox requires macOS, Linux, or WSL2; on native Windows the npm `claude.cmd` launch is verified and a direct `claude.exe` launch is pending verification. The optional --autocompact flag requires claude 2.1.221 or newer.

Workflow steps

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

  1. Write the brief
  2. Dispatch
  3. Wait
  4. Review
  5. Land

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:

    • claude
    • node
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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.

  • Compatibility

    Requires the `claude` CLI (Claude Code) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Claude's shell sandbox requires macOS, Linux, or WSL2; on native Windows the npm `claude.cmd` launch is verified and a direct `claude.exe` launch is pending verification. The optional --autocompact flag requires claude 2.1.221 or newer.

    From compatibility in the SKILL.md frontmatter.

Context cost

Claude Delegate loads about 2.4k tokens when it runs, and up to ~9.6k if it reads all its reference files. Until then it costs about 148 tokens; SKILL.md has 1,059 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~148
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.6k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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). 1,059 words, ~2,415 tokens.

Download SKILL.mdSave it as .claude/skills/claude-delegate/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
claude-delegate
description
Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the `claude` CLI — for example, "have another Claude implement this", "delegate this to Claude Code", or "run this queue through a separate Claude session." Do not trigger merely because the current orchestrator is Claude, and do not use when the user asks the current Claude to implement directly without delegation.
compatibility
Requires the `claude` CLI (Claude Code) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Claude's shell sandbox requires macOS, Linux, or WSL2; on native Windows the npm `claude.cmd` launch is verified and a direct `claude.exe` launch is pending verification. The optional --autocompact flag requires claude 2.1.221 or newer.
license
MIT
metadata.version
0.5.0

Claude Delegate

You are the orchestrator. Delegate one bounded coding task to a separate implementer — a Claude Code CLI session — then review what it produced and land it yourself. You write the brief and own the judgment; the separate Claude session edits the working tree; you verify and commit.

This skill is not a signal for the current Claude to implement directly. Use it only after the human explicitly asks for delegation to another Claude Code process or session.

When not to use this

  • The human asked the current agent to implement the task directly.
  • The task is small enough to do inline and the human did not request delegation.
  • The claude CLI is missing or unauthenticated (claude auth status).
  • The task needs a stronger host boundary than Claude Code's tool permissions and shell-only sandbox provide. Use an isolated container or VM for that requirement.

Prerequisites

  1. claude --version succeeds.
  2. claude auth status reports an authenticated session. On macOS the live credentials sit in the login Keychain; when the orchestrator's own sandbox blocks Keychain access (Codex's sandbox does), claude falls back to a possibly stale credentials file and reports loggedIn: false even though the login is valid. Re-run the check — and the dispatch itself — with that sandbox escalated or outside it before concluding the CLI is unauthenticated.
  3. The target repository is the directory passed with --cd.
  4. On Linux/WSL2, Claude's sandbox dependencies are installed. The normal relay profile is configured to fail when the sandbox is unavailable instead of silently running shell commands unsandboxed. Existing merged settings can still affect the effective boundary.

The loop

1. Write the brief

The separate session has no orchestrator chat history. It receives the brief on stdin and can inspect the target working tree.

Claude Code automatically discovers the target project's CLAUDE.md and normal local Claude configuration because the relay does not use --bare. It does not generically auto-load AGENTS.md. Read AGENTS.md yourself and copy every load-bearing constraint and the real gate commands into the brief. Tell the implementer not to commit. Keep one task per brief.

Template and details: references/writing-the-brief.md.

2. Dispatch
bash
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# review/diagnosis only:                 add --read-only
# continue the latest session:           add --resume-last
# continue the recorded session:         add --session <id>
# choose limits:                         add --max-turns 40 --max-budget-usd 10
# set the auto-compact window:           add --autocompact 400k
# hard relay deadline:                   add --timeout 2h
# inspect every option:                  node .../relay.mjs --help

<skill-dir> is this installed skill directory, the folder containing this SKILL.md.

The relay runs claude -p --output-format stream-json --verbose, sends the brief through stdin, and writes artifacts under the system temp directory by default. It never uses --bg or --bare, and it never commits. See references/dispatch-and-poll.md.

--autocompact <auto|tokens> passes Claude Code's auto-compact window setting on every new or resumed invocation, and needs Claude Code 2.1.221 or newer — older builds fail the dispatch with unknown option '--autocompact'. The installed CLI owns the accepted range (auto, or 100k–1M tokens); the relay records the requested value but does not claim that Claude applied or enforced it.

3. Wait

The relay blocks until Claude exits. Use the orchestrator's background-command facility, or run it in the foreground and wait. Completion means the process exited and result.json exists.

  • A pre-run usage error exits 2 and writes no result.json.
  • A missing claude exits 127 and writes status: "claude_unavailable".
  • Timeout and caught relay signals terminate the whole implementer process tree and preserve an outcome artifact.

Read finalMessage, touchedFiles, resultSubtype, and the raw artifact paths from result.json.

4. Review

Treat the implementer's report and gate outcomes as claims:

  • Review edits to existing tests before a green gate means anything.
  • Re-run the project's actual gates yourself.
  • Read the complete diff against the brief, starting with touchedFiles.
  • Inspect untracked and staged content as well as the ordinary diff.
  • Run relevant guard skills if installed.

Full checklist: references/review-and-land.md.

5. Land

The orchestrator commits only after the gates pass and the diff holds. For rework, resume the same Claude session with a delta brief:

bash
echo "Keep the implementation, replace the mocked DB test with the migrated fixture, and remove the
unused import." | node "<skill-dir>/scripts/relay.mjs" --session <id> --cd /path/to/repo

Review a resumed run exactly like the first run.

Show full SKILL.md (438 more words)Show less

Permission profiles

The normal profile is deliberately explicit:

  • acceptEdits permission mode.
  • Built-in tools restricted to Read, Glob, Grep, Edit, Write, and the platform shell.
  • On macOS, Linux, and WSL2, Claude's shell sandbox is enabled with startup failure on missing dependencies and no unsandboxed retry. Commands that stay sandboxed are auto-approved so ordinary gates can run headlessly. The sandbox governs shell processes and their children only; merged local or managed sandbox settings can add effective paths or exclusions.
  • Configured MCP discovery and Claude.ai connectors are disabled, all MCP tools are denied, and skills, commands, and Claude's Agent tool are unavailable to the child. Project CLAUDE.md, hooks, normal authentication, session persistence, and other local settings still load.
  • String rules deny common direct shell forms of git commit, git push, and nested claude, plus any command containing claude-delegate. Aliases, scripts, and wrappers can bypass them, so they are only a speed bump; the brief's no-commit instruction and orchestrator review remain the boundary.

Native Windows does not support Claude's shell sandbox. The relay restricts the tool surface and pre-approves PowerShell so the run remains non-interactive, but that shell is not OS-isolated. Native claude.exe and npm claude.cmd launch paths are implemented. The claude.cmd path has a recorded native Windows run (see the README's Verification status); a directly spawned claude.exe is not yet verified.

--read-only uses plan mode with only Read, Glob, and Grep. It removes edit, write, and shell paths, then compares parsed git porcelain and fingerprints the working-tree identity and index entries of Git-visible paths that were already dirty. readOnlyViolation is true when either signal proves a change, false when coverage is complete and detects none, and null when coverage is incomplete. This is a reporting tripwire, not an OS boundary: ignored paths and perfect restores are outside it, local hooks can write, and concurrent changes cannot be attributed to Claude.

--dangerously-skip-permissions is an explicit opt-in to Claude's bypassPermissions mode. The restricted tool surface, direct commit/push deny rules, and supported-platform shell sandbox remain, but direct file tools can cross normal permission boundaries. Use it only with the human's explicit acceptance.

Complementary to native Claude features

Claude subagents, agent teams, and background sessions are useful when the current Claude environment is already the orchestrator and native coordination is the goal. This skill is complementary: it provides a cross-orchestrator contract — self-contained brief → dispatch → artifacts → review → land — and keeps the commit with the orchestrator.

References

© 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/claude-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

Compare with similar skills

Claude Delegate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Claude Delegate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Claude Delegate this skillamElnagdy/delegate-skills2.3k—~2.4kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from amElnagdy/delegate-skills

All 18 skills in this repo
  • Aider Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to Aider (aider) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~3k tokens
    Auto-check passed
  • Qoder Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Qoder CLI (qodercli) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed
  • Warp Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~2.6k tokens
    Auto-check passed
  • Agy Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Cline Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Cline coding agent CLI (cline) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Codex Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself.

    2.3k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Claude Delegate

What does Claude Delegate do?

Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Claude Delegate is an agent skill from amElnagdy/delegate-skills. Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself.

When should I use Claude Delegate?

Claude Delegate fits situations like: explicitly asks to delegate implementation to Claude Code; another Claude session; the claude CLI — for example; have another Claude implement this.

How do I install Claude Delegate in Claude Code?

Run `npx skills add amElnagdy/delegate-skills --skill claude-delegate -a claude-code`. Or copy the skill folder (skills/claude-delegate in amElnagdy/delegate-skills) into .claude/skills/claude-delegate in your project. Claude Code loads it when a task matches its description.

How do I install Claude Delegate in Codex?

Run `npx skills add amElnagdy/delegate-skills --skill claude-delegate -a codex`. Or copy the skill folder (skills/claude-delegate in amElnagdy/delegate-skills) into .agents/skills/claude-delegate in your project. Codex loads it when a task matches its description.

Can I use Claude Delegate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amElnagdy/delegate-skills --skill claude-delegate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claude-delegate, .gemini/skills/claude-delegate, .github/skills/claude-delegate and .opencode/skills/claude-delegate in your project.

What does Claude Delegate need to run?

Going by SKILL.md and its folder, Claude Delegate needs JavaScript for the scripts in its folder and the command-line tools its instructions call (claude, node and git). Our summary lists: Node.js. Compatibility (from SKILL.md): Requires the `claude` CLI (Claude Code) installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Claude's shell sandbox requires macOS, Linux, or WSL2; on native Windows the npm `claude.cmd` launch is verified and a direct `claude.exe` launch is pending verification. The optional --autocompact flag requires claude 2.1.221 or newer..

Does Claude Delegate access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Claude Delegate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Claude Delegate use?

Claude Delegate is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Claude Delegate use?

About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.2k tokens, read only when the agent opens those files.

What are the alternatives to Claude Delegate?

Skills that share tags, products or a category with Claude Delegate: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Claude Delegate?

amElnagdy (a GitHub user) maintains it in amElnagdy/delegate-skills, which has 2,336 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: amElnagdy/delegate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.