Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →amelnagdy/grok-delegate
Delegate a coding task to the Grok Build CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Grok — phrasings like "have Grok do X", "delegate this to Grok", "run it through Grok", "use Grok Build to implement/fix/refactor", or "have grok CLI do this" — or to run a queue of coding tasks through Grok while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE f
Passed 13 of 19 test cases with the skill, and 3 of 19 without it.
and 13 more in the full report
12 fixed3 passed either way7 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 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We ran a relay script dispatch, but the process exited with code 127. What artifact is generated and what status value should we expect in it?
| Checked | Without skill | With skill |
|---|---|---|
| States that result.json is created despite exit code 127. | Passed | Passed |
| Identifies grok_unavailable as the status string in result.json. | Missed | Passed |
The instructions your model reads when the skill loads.
For a trusted repository rejected by Git's ownership check, the relay supports
--trust-git-root <exact-worktree-root>. This opt-in affects only relay Git checks, without persistent
Git config or Grok permission changes. See dispatch and poll.
You are the orchestrator. This skill lets you hand a bounded coding task to a separate
implementer — the Grok Build CLI (grok) — then review what it produced and land it yourself. You
write the brief and own the judgment; Grok does the typing under an explicit autonomy profile; you
verify and commit.
Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell command and read a file, so it works the same whether you are Claude Code, Cursor, OpenCode with a selected model, or any comparable agent. (It is designed for Claude Code and Cursor; treat other orchestrators as designed-for, not yet proven.)
grok CLI is not installed, not authenticated, or the account lacks Grok Build beta access.grok version succeeds. If not, install on any platform with
npm i -g @xai-official/grok (or use the installer from xAI's official Grok CLI docs) and
authenticate (grok login, or grok login --device-auth on headless hosts, or set
XAI_API_KEY).grok is on PATH. command -v grok shows the active binary and grok version
its version — the relay records the version it ran into result.json, so a stale binary is visible
after the fact.--cd at) the target git repository.Run these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.
Grok sees only the text you send — no orchestrator chat history, no shared context. Everything the
test cases passed, vs 3 / 19 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.