New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Warp Delegate

by amElnagdy in 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.

MITAuto-check passed

Install Warp Delegate

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

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

GitHub CLI
$ gh skill install amElnagdy/delegate-skills warp-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/warp-delegate .claude/skills/warp-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
warp-delegate
GitHub stars
2.3k
Used in
3 other repos
Token cost
~2.6k tokens
SKILL.md length
1,225 words
Files
6 (incl. scripts, references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: Write the brief → Dispatch → Wait for completion → …
  • Wants to hand implementation work to Warp - phrasings like have Warp implement X
  • SKILL.md covers The binary is oz, not warp, When NOT to use this, Prerequisites (check once) and Choose the model (optional), plus 4 more sections
  • Runs JavaScript scripts from its folder; calls node and git; needs WARP_API_KEY

What it does

Warp Delegate is an agent skill from 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. Use this whenever the user wants to hand implementation work to Warp - phrasings like "have Warp implement X", "delegate this to the Warp CLI", "run it through Warp", "use oz to implement/fix/refactor" - or wants to run a queue of coding tasks through Warp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without…

Its SKILL.md is about 2.6k 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 oz CLI (Warp Agent CLI) installed and authenticated (oz login, or WARPAPIKEY for a headless host; Warp AI features need an eligible Warp plan or…

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

  • Wants to hand implementation work to Warp - phrasings like have Warp implement X
  • Delegate this to the Warp CLI
  • Run it through Warp
  • Use oz to implement/fix/refactor -

Example prompts

  • “have Warp implement X”
  • “delegate this to the Warp CLI”
  • “run it through Warp”
  • “/warp-delegate”

Requirements

  • Node.js
  • A credential in WARP_API_KEY
  • Compatibility (from SKILL.md): Requires the `oz` CLI (Warp Agent CLI) installed and authenticated (`oz login`, or `WARP_API_KEY` for a headless host; Warp AI features need an eligible Warp plan or your own provider key), Node 18+, and git. 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).

Workflow steps

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

  1. Write the brief
  2. Dispatch
  3. Wait for completion
  4. Review - do not trust the self-report
  5. Land it

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:

    • node
    • git

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

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.warp.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • WARP_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires the `oz` CLI (Warp Agent CLI) installed and authenticated (`oz login`, or `WARP_API_KEY` for a headless host; Warp AI features need an eligible Warp plan or your own provider key), Node 18+, and git. 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).

    From compatibility in the SKILL.md frontmatter.

Context cost

Warp Delegate loads about 2.6k tokens when it runs, and up to ~8.8k if it reads all its reference files. Until then it costs about 160 tokens; SKILL.md has 1,225 words of instructions outside code blocks.

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

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,225 words, ~2,578 tokens.

Download SKILL.mdSave it as .claude/skills/warp-delegate/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
warp-delegate
description
Delegate a coding task to the Warp Agent CLI (`oz`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Warp - phrasings like "have Warp implement X", "delegate this to the Warp CLI", "run it through Warp", "use oz to implement/fix/refactor" - or wants to run a queue of coding tasks through Warp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or for the interactive `warp` TUI (this skill drives the headless `oz agent run`, not the terminal app).
compatibility
Requires the `oz` CLI (Warp Agent CLI) installed and authenticated (`oz login`, or `WARP_API_KEY` for a headless host; Warp AI features need an eligible Warp plan or your own provider key), Node 18+, and git. 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).
license
MIT
metadata.version
0.5.0

Warp Delegate

You are the orchestrator. Delegate a bounded coding task to a separate implementer - the Warp Agent 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 conversation; you verify and commit.

The loop needs only a shell command and file access, so any comparable orchestrator can drive it.

The binary is oz, not warp

Warp ships two different programs, and only one of them can be delegated to:

  • oz - the Warp Agent CLI. Headless and scriptable; oz agent run executes an agent against a local directory. This is what the relay drives.
  • warp - the interactive Warp TUI. It requires a terminal device, has no prompt or print flag (its only options are --resume, --auto-approve, --api-key, and the provider-key commands), and exits with Device not configured when stdin is a pipe. It cannot be relayed.

If oz is missing but warp is installed, you have the TUI, not the CLI.

When NOT to use this

  • The task is small enough to do inline; delegation overhead is not worth it.
  • The oz CLI is not installed or authenticated.
  • You need a sandboxed or read-only implementer. oz agent run has no sandbox, no permission mode, and no read-only run - see Autonomy and permissions.
  • The work must stay off Warp's servers. oz agent run uploads an end-of-run workspace snapshot unless --no-snapshot is passed, and conversations live server-side.

Prerequisites (check once)

  1. Install the Warp Agent CLI - see https://docs.warp.dev/cli/.
  2. Authenticate: oz login, or set WARP_API_KEY for CI, a container, or any headless host.
  3. Confirm the account has AI quota. A working login is not enough - unlike the other CLIs in this package. oz whoami can succeed while every dispatch fails with In order to use Warp's AI features, subscribe to a Warp plan, or bring your own inference. Warp records this internally as QuotaLimit / "lack of AI quota", so it is a credit condition on the account rather than a CLI-specific entitlement: oz runs the same agent harness as the Warp app and draws on the same account, plan, and credits. Check that oz whoami names the account holding the plan - if it does not, oz logout && oz login fixes it. Otherwise confirm the plan's AI credits are not spent, or store your own provider key - warp --set-provider-api-key <openai|anthropic|google|grok>, or /api-keys inside the TUI. Bring-your-own-key needs no paid Warp plan.
  4. Confirm oz --version succeeds and oz whoami prints your user.
  5. Work in, or point --cd at, the target git repository.

On macOS the CLI is distributed as a signed Developer ID binary; a first run may be held by Gatekeeper until it is approved.

Choose the model (optional)

Omit --model to use Warp's configured default. To pick another, choose an id from oz model list and pass it verbatim. The relay accepts letters, digits, and . _ : / - only, so a value cannot be mistaken for another oz flag.

The loop

Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.

1. Write the brief

Warp 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 it not to commit. Keep one task per brief. The brief is delivered as the --prompt value on argv, so it is visible in the host process list - keep secrets out of it and reference workspace files instead. See references/writing-the-brief.md.

2. Dispatch

Use the bundled relay. It runs oz agent run --output-format ndjson, captures the event stream, and writes result.json. (<skill-dir> is the installed folder containing this SKILL.md.)

bash
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# choose a model:                          add --model <id from oz model list>
# use an agent profile:                    add --profile <id>
# label the run:                           add --name <label>
# continue an existing conversation:       add --conversation <id> (delta brief only)
# base the run on a Warp skill:            add --skill <name|repo:name|org/repo:name>
# start MCP servers:                       add --mcp <path-or-inline-json>  (repeatable)
# suppress the workspace snapshot upload:  add --no-snapshot
# 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 relay pins the workspace with both the child process's cwd and Warp's own --cwd. It 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 oz 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 oz exits 127 and writes status: "warp_unavailable".

Trust process state and the working tree over a progress display. Completion means the process exited and result.json exists. Warp's report is the finalMessage field in result.json (also printed on stdout between the report markers); the raw event stream is always in events.jsonl.

Show full SKILL.md (480 more words)Show less
4. Review - do not trust the self-report

Treat Warp'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.

Because there is no read-only mode to fall back on, the diff is the only record you get - and it records what git can see in the workspace afterward, not everything the run did. Dispatch from a clean tree so the two are as close as they can be. 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 --conversation <id> using the conversationId from result.json, then review again.

Autonomy and permissions

oz agent run has no sandbox, no permission mode, and no read-only mode. A headless run reads, writes, edits, and executes commands with your own user permissions and never prompts. There is nothing in the CLI to restrict that surface, so this relay ships no --read-only flag - offering one would imply an enforcement that does not exist. The controls you actually have are:

  1. Scope by directory. --cd pins the workspace, and the relay passes it to Warp's own --cwd. Treat this as aim, not a fence: on oz 0.2026.05.27 shell commands did run in the pinned workspace, but the agent's file tool resolved bare relative paths against $HOME. Name absolute paths in the brief - see references/writing-the-brief.md.
  2. Review the diff. touchedFiles is git status --porcelain taken after the run - post-run, git-visible worktree state, not a log of what the agent did. It cannot show an ignored file, an edit the run made and then reverted, or a write outside the repository (see item 1), and it carries anything that was already dirty before dispatch. Dispatch from a clean tree so those are the same set, and treat the diff as the best available record, not a complete one.
  3. Snapshot egress. --no-snapshot forwards Warp's flag so the end-of-run workspace snapshot is not uploaded. Without it, the upload is Warp's default.

--auto-approve belongs to the interactive warp TUI and has no bearing on oz agent run.

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 Warp'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

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

Used in 3 other repositories

We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in amElnagdy/delegate-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Warp 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.

Warp Delegate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Warp Delegate this skillamElnagdy/delegate-skills2.3k3 repos~2.6kAutomated safety check: PassMIT
Delegate Workpaperclipai/paperclip99k—~372Automated safety check: PassMIT
Event Delegationthedaviddias/Front-End-Checklist74k—~500Automated safety check: PassMIT
Delegating To Agentssickn33/agentic-awesome-skills47k1 repos~1kAutomated safety check: PassMIT
Opencode Delegatesickn33/agentic-awesome-skills47k1 repos~2.8kAutomated safety check: PassMIT
Cline Delegatesickn33/agentic-awesome-skills47k1 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • Delegate Work

    paperclipai/paperclip

    Delegate user-requested work to an existing Paperclip agent, with a durable task reference and clear execution expectations.

    99k GitHub stars~372 tokensUpdated today
    Auto-check passed

  • Event Delegation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content.

    74k GitHub stars~500 tokensUpdated 2 days ago
    Auto-check passed

  • Delegating To Agents

    sickn33/agentic-awesome-skills

    Delegate bounded work to other AI agents while preserving context, ownership, and progress checks.

    47k GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed

  • Opencode Delegate

    sickn33/agentic-awesome-skills

    Delegate coding tasks to the OpenCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

    47k GitHub starsUsed in 1 repo~2.8k tokens
    Auto-check passed

  • Cline Delegate

    sickn33/agentic-awesome-skills

    Delegate coding tasks to the Cline CLI (cline) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

    47k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Grok Delegate

    sickn33/agentic-awesome-skills

    Delegate coding tasks to the Grok Build CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

    47k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-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 3 repos~3k tokens
    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 starsUsed in 3 repos~2.5k 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 3 repos~1.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 starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Claude Delegate

    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.

    2.3k GitHub starsUsed in 1 repo~2.4k tokens
    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 starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Questions about Warp Delegate

What does Warp Delegate do?

Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself. Warp Delegate is an agent skill from 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.

When should I use Warp Delegate?

Warp Delegate fits situations like: wants to hand implementation work to Warp - phrasings like have Warp implement X; delegate this to the Warp CLI; run it through Warp; use oz to implement/fix/refactor -.

How do I install Warp Delegate in Claude Code?

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

How do I install Warp Delegate in Codex?

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

Can I use Warp 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 warp-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/warp-delegate, .gemini/skills/warp-delegate, .github/skills/warp-delegate and .opencode/skills/warp-delegate in your project.

What does Warp Delegate need to run?

Going by SKILL.md and its folder, Warp Delegate needs JavaScript for the scripts in its folder, the command-line tools its instructions call (node and git) and credentials named WARP_API_KEY. Our summary lists: Node.js; A credential in WARP_API_KEY. Compatibility (from SKILL.md): Requires the `oz` CLI (Warp Agent CLI) installed and authenticated (`oz login`, or `WARP_API_KEY` for a headless host; Warp AI features need an eligible Warp plan or your own provider key), Node 18+, and git. 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)..

Does Warp Delegate access the network?

SKILL.md names 1 domain. As links in the text: docs.warp.dev. This is read from the text; nothing was executed.

Is Warp 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 Warp Delegate use?

Warp 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 Warp Delegate use?

About 2.6k tokens (SKILL.md is roughly 10k 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 6.3k tokens, read only when the agent opens those files.

What are the alternatives to Warp Delegate?

Skills that share tags, products or a category with Warp Delegate: Delegate Work (paperclipai/paperclip, 99k stars), Event Delegation (thedaviddias/Front-End-Checklist, 74k stars), Delegating To Agents (sickn33/agentic-awesome-skills, 47k stars) and Opencode Delegate (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Warp Delegate?

amElnagdy (a GitHub user) maintains it in amElnagdy/delegate-skills, which has 2,328 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.