Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →amelnagdy/vibe-delegate
Delegate a coding task to the Mistral Vibe CLI (`vibe`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Vibe — phrasings like "have Vibe implement X", "delegate this to Vibe", "run it through Mistral Vibe", "use vibe to implement/fix/refactor" — or wants to run a queue of coding tasks through Vibe while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code writt
Passed 16 of 19 test cases with the skill, and 6 of 19 without it.
and 9 more in the full report
12 fixed7 passed either way3 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.
If an invalid argument combination causes a pre-run usage error in relay.mjs prior to starting Vibe, what integer exit code does the relay process emit?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies exit code 2 | Missed | Passed |
The instructions your model reads when the skill loads.
You are the orchestrator. Hand a bounded coding task to a separate implementer — the Mistral
Vibe CLI (vibe) — then review what it produced and land it yourself. You write the brief and own
the judgment; Vibe does the typing 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.
vibe CLI is not installed or authenticated.uv, then Mistral Vibe:
uv tool install mistral-vibevibe --setup, or set MISTRAL_API_KEY in the environment.vibe --version succeeds.--cd at, the target git repository.Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
Vibe 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 Vibe not to commit. Keep one task per brief. See references/writing-the-brief.md.
Default mode cannot approve most shell commands headlessly, so the orchestrator runs the gates. Ask
Vibe to run them only when the human explicitly authorized --full-access.
For Codex orchestration of background work, install and configure the separate codex-background support utility first. If its MCP tools or registry are missing, stop and report the setup requirement; do not silently fall back to model-driven polling. Then invoke its
test cases passed, vs 6 / 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.