Delegate bounded coding tasks to Mistral Vibe and review

Lets an orchestrating agent hand a bounded coding task to the Mistral Vibe CLI (vibe) as a separate implementer, then review what it produced and land it itself. In --prompt mode the relay always sets one of three explicit agent profiles rather than trusting Vibe's own default: the default run passes --agent accept-edits, which approves Vibe's built-in file edits inside the target worktree but still denies most approval-gated shell commands headlessly - including most project gates, which means the orchestrator itself must run them, not Vibe; --plan-only passes --agent plan for read-only review, exploration, or planning; and --full-access passes --agent auto-approve, disabling Vibe's tool approvals entirely and permitting arbitrary shell/tool execution under the user's own account - reserved for explicitly human-authorized runs that genuinely need it. --trust is always passed to suppress interactive directory-trust prompts in headless runs, but the skill is explicit that this is not a sandbox and grants no tool permissions by itself; touchedFiles and the diff remain the actual record of what changed, inspected after every run regardless of which profile was used.

Dispatch wraps Vibe's headless --prompt mode and writes a structured result.json to a temp directory by default; the relay never commits. Cost controls are built into dispatch itself: --max-turns <n> caps agentic turns, and --max-price <usd> / --max-tokens <n> set an indicative price threshold or token cap on the run. Failure states are explicit in result.json: a missing vibe binary writes status: vibe_unavailable, the relay's own watchdog timing out writes status: timeout, and terminating the relay on POSIX writes status: aborted only after it has stopped Vibe's process tree first. Rework resumes the most recent session (--resume-last) or a specific one (--session <id>) with just a delta brief.

Use it to delegate a bounded coding task to a separate vibe implementer and then review its diff yourself, when the user explicitly asked for delegation to this implementer. Do NOT use it when the task is small enough to do inline and delegation overhead isn't worth it, or when the vibe CLI is not installed or authenticated.

The brief states the goal, current state, what to change, what to leave untouched, the project's real gate commands, and a report contract telling Vibe not to commit - and, since default mode cannot approve most shell commands headlessly, the brief should ask Vibe to run gates itself only when the human has explicitly authorized --full-access. Dispatch:

node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo

Output is result.json with status, finalMessage, and touchedFiles (the review starting point regardless of agent profile used).

Wraps the Mistral Vibe CLI, installed via uv tool install mistral-vibe (after installing uv itself), authenticated with vibe --setup or a MISTRAL_API_KEY environment variable. Can apply a fleet lane's dials from a companion delegate-setup configuration.

Orchestrating agents that need to delegate a scoped coding task to Mistral Vibe under a deliberately chosen agent profile - edit-only by default, plan-only for exploration, or fully authorized when the human explicitly grants it - while keeping review-and-commit authority. Adapted from the community amElnagdy/delegate-skills repository under the MIT license; this catalog entry is a docs-only import, since the executable scripts/relay.mjs is not bundled here.