Install any skill in seconds. Free to start, no credit card required.
Get Started Free →amelnagdy/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. 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
Passed 13 of 16 test cases with the skill, and 8 of 16 without it.
and 5 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
After the delegated CLI agent finishes execution and writes `result.json`, which specific field in the output JSON should be checked first to review the modified files?
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies touchedFiles as the primary JSON field for file diff review. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
pi CLI is not installed or authenticated.--read-only
restricts the tool surface, but a write-capable run executes without prompts.npm install -g @earendil-works/pi-coding-agent./login inside pi for a subscription provider, or an API-key environment
variable / pi's auth file for an API-key provider.pi --version succeeds.--cd at, the target git repository.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.
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
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
test cases passed, vs 8 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.