# Vibe Delegate

Delegate a coding task to the Mistral Vibe CLI (`vibe`) as a background implementer...

- Repository: https://github.com/amElnagdy/delegate-skills (2546 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -g -a claude-code -y`
Codex: `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -g -a codex -y`
Cursor: `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -g -a cursor -y`
Gemini CLI: `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -g -a gemini-cli -y`

## Description

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 written directly without delegating.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Vibe Delegate

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.

## When NOT to use this

- The task is small enough to do inline; delegation overhead is not worth it.
- The `vibe` CLI is not installed or authenticated.

## Prerequisites (check once)

1. Install [`uv`](https://docs.astral.sh/uv/getting-started/installation/), then Mistral Vibe:
   - `uv tool install mistral-vibe`
2. Configure your API key with `vibe --setup`, or set `MISTRAL_API_KEY` in the environment.
3. Confirm `vibe --version` succeeds.
4. Work in, or point `--cd` at, the target git repository.

## The loop

Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.

### 1. Write the brief

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](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`.

### 2. Dispatch

The rest: https://github.com/amElnagdy/delegate-skills/blob/HEAD/skills/vibe-delegate/SKILL.md