pi-delegate
Delegate a coding task to the Pi coding agent CLI (`pi`) as a background implementer, then review its diff and land it yourself.
Install / Use
npx skills add amElnagdy/delegate-skills --skill pi-delegateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of pi-delegate
pi-delegate scores 89/100 on our quality scale, 1608th of 4,698 Development & Engineering skills we index (top 35%).
Its SKILL.md is 6.6 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 pi-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.
pi-delegate compared with similar skills
All 4 of these similar skills score higher than pi-delegate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pi-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 pi-delegate?
- Run
npx skills add amElnagdy/delegate-skills --skill pi-delegate. The install tabs above show the steps for each supported agent. - Which AI agents does pi-delegate work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pi-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 pi-delegate still maintained?
- The repository was last updated about 2 months ago, so pi-delegate is actively maintained.
Skill content
View source on GitHubname: pi-delegate
description: >-
Delegate a coding task to the Pi coding agent CLI (pi) as a background implementer, then review
its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Pi -
phrasings like "have Pi implement X", "delegate this to pi", "run it through Pi", or "use pi to
implement/fix/refactor" - or wants to run a queue of coding tasks through Pi 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
metadata:
version: 0.5.0
Pi Delegate
You are the orchestrator. Delegate a bounded coding task to a separate implementer - the Pi coding 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 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
piCLI is not installed or authenticated. - You need a sandboxed implementer. Pi has no sandbox and no permission modes;
--read-onlyrestricts the tool surface, but a write-capable run executes without prompts.
Prerequisites (check once)
- Install pi with
npm install -g @earendil-works/pi-coding-agent. - Authenticate:
/logininside pi for a subscription provider, or an API-key environment variable /pi's auth file for an API-key provider. - Confirm
pi --versionsucceeds. - Work in, or point
--cdat, the target git repository.
Choose the model (optional)
Omit --model to use pi's configured default. To pick another, choose from pi --list-models
and pass an explicit id or pattern like <provider>/<model-id> or sonnet:high. The relay
accepts letters, digits, and . _ : / - only (the value reaches a shell on Windows), so glob
patterns with * are not forwarded.
The loop
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
1. Write the brief
Pi 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 pi not to commit. Keep one task per brief.
Pi auto-loads AGENTS.md/CLAUDE.md context files from the workspace and its parents, so repo
instructions reach it without inlining. See
references/writing-the-brief.md.
2. Dispatch
Use the bundled relay. It pipes the brief to pi --mode json on stdin, captures the JSON 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
# choose a model: add --model <id from pi --list-models>
# choose a provider: add --provider <name>
# read-only run (review/diagnosis): add --read-only
# trust project .pi resources: add --approve
# 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. 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 pi 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 pi exits 127 and writes status: "pi_unavailable".
Trust process state and the working tree over a progress display. Completion means the process
exited and result.json exists. Pi's full report is the finalMessage field in result.json
(also printed in full on stdout between the report markers).
4. Review - do not trust the self-report
Treat pi'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
Pi has no sandbox and no permission modes. A default headless run reads, writes, edits, and executes shell commands with no prompts - the controls are:
--read-onlyrestricts pi's callable tools to--tools read,grep,find,lsacross built-in, extension, and custom tools. Installed extension code still runs with the user's host permissions.- The relay passes
--no-approveby default, so project.pisettings, extensions, and skills stay untrusted.--approveis the explicit opt-in for a repository the user trusts. touchedFilesand the diff are the record of what changed. Inspect them after every 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 pi'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, stdin delivery, 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 pi 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.
