Vibe Delegate
Delegate a coding task to the Mistral Vibe CLI (`vibe`) as a background implementer...
Install
npx skills add amElnagdy/delegate-skills --skill vibe-delegate -g -a claude-code -y- Repository
- amElnagdy/delegate-skills2.5k
- Category
- Engineering
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 1,676 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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
vibeCLI is not installed or authenticated.
Prerequisites (check once)
- Install
uv, then Mistral Vibe:uv tool install mistral-vibe
- Configure your API key with
vibe --setup, or setMISTRAL_API_KEYin the environment. - Confirm
vibe --versionsucceeds. - Work in, or point
--cdat, 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.
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.
