New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Vibe Delegate

by amElnagdy in amElnagdy/delegate-skills

Delegate a coding task to the Mistral Vibe CLI (vibe) as a background implementer, then review its diff and land it yourself.

MITAuto-check passedDevelopment

Install Vibe Delegate

skills CLI
$ npx skills add amElnagdy/delegate-skills --skill vibe-delegate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install amElnagdy/delegate-skills vibe-delegate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/amElnagdy/delegate-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vibe-delegate .claude/skills/vibe-delegate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vibe-delegate
GitHub stars
2.3k
Token cost
~1.6k tokens
SKILL.md length
689 words
Files
6 (incl. scripts, references)
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Delegate a coding task to the Mistral Vibe CLI (vibe) as a background implementer, then review its diff and land it yourself.

  • Works in 5 steps: Write the brief → Dispatch → Wait for completion → …
  • Wants to hand implementation work to Vibe — phrasings like have Vibe implement X
  • SKILL.md covers When NOT to use this, Prerequisites (check once), The loop and Autonomy and permissions, plus 2 more sections
  • Runs JavaScript scripts from its folder; calls node and uv; needs MISTRAL_API_KEY

What it does

Vibe Delegate is an agent skill from amElnagdy/delegate-skills. 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…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/dispatch-and-poll.md`, `references/multi-task-queues.md` and `references/review-and-land.md`).

It sits in Development. It works with Mistral AI. The repository describes itself as: Delegate a coding task to a separate coding agent CLI, review the diff, land the commit yourself — one per implementer. The licence is MIT.

When your agent uses it

  • 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 —

Example prompts

  • “have Vibe implement X”
  • “delegate this to Vibe”
  • “run it through Mistral Vibe”
  • “/vibe-delegate”

Requirements

  • Node.js
  • A credential in MISTRAL_API_KEY

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Write the brief
  2. Dispatch
  3. Wait for completion
  4. Review — do not trust the self-report
  5. Land it

What it can do on your machine

Read from SKILL.md and the folder at commit 8ef0210. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node
    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.astral.sh

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • MISTRAL_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vibe Delegate loads about 1.6k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 136 tokens; SKILL.md has 689 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~136
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from amElnagdy/delegate-skills at commit 8ef0210, republished under its MIT licence (© amElnagdy). 689 words, ~1,637 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-delegate/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
vibe-delegate
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.
license
MIT
metadata.version
0.5.0

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, 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.

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

Use the bundled helper. It wraps Vibe's headless --prompt mode, captures the structured event stream, and writes result.json. (<skill-dir> is the installed folder containing this SKILL.md.)

bash
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# limit turns for cost control:           add --max-turns <n>
# indicative price threshold/token cap:  add --max-price <usd> --max-tokens <n>
# planning/read-only:                     add --plan-only
# unrestricted shell and tools:           add --full-access (explicit authorization required)
# resume the most recent session:         add --resume-last  (delta brief only)
# resume a specific session:              add --session <id> (delta brief only)
# see all options:                        node .../relay.mjs --help

The child process's cwd pins the workspace. The relay writes artifacts under the system temp dir by default and never commits. See references/dispatch-and-poll.md.

3. Wait for completion

The helper blocks until Vibe finishes. Run it with the orchestrator's background-command facility, or background it in the shell and poll for result.json. A pre-run usage error exits 2 and writes no result; a missing vibe exits 127 and writes status: "vibe_unavailable". The watchdog writes status: "timeout"; terminating the relay on POSIX writes status: "aborted" after stopping Vibe's process tree.

Trust process state and the working tree over a progress display. Completion means the process exited and result.json exists.

4. Review — do not trust the self-report

Treat Vibe's final message and gate claims as claims:

  • Re-run the project's gates yourself.
  • Read the diff against the brief, starting with touchedFiles.
  • Run relevant guard skills if installed.
  • Round-trip migrations and grep for dangling references after removals or renames.

See references/review-and-land.md.

Show full SKILL.md (267 more words)Show less
5. Land it

The implementer edits the working tree; the orchestrator commits. Commit only after the gates pass and the diff holds. If rework is needed, send a delta brief with --resume-last or --session <id>, then review again.

Autonomy and permissions

In --prompt mode the relay always sets the agent profile explicitly:

Relay flagWhat Vibe getsUse when
(default)--agent accept-editsNormal implementation — built-in file edits are approved
--plan-only--agent planRead-only review, exploration, or planning
--full-access--agent auto-approveExplicitly authorized runs that need arbitrary shell/tools

Default mode lets Vibe edit files inside the target worktree. Approval-gated shell commands, including most project gates, are denied headlessly; the orchestrator runs the gates. --full-access disables Vibe's tool approvals and permits arbitrary shell/tool execution under the user account; use it only with explicit human authorization. Always inspect touchedFiles and the diff after a run.

--trust is always passed to prevent interactive directory-trust prompts in headless runs. It is not a sandbox and does not grant tool permissions.

Authorization model

Delegation is something the human opts into. Once they have ("run this queue", "proceed"), committing verified, gate-passing work is the agreed contract. Two limits remain: surface, don't absorb (report Vibe's design decisions, defensible-but-unasked turns, and non-blocking nitpicks) and stop for scope changes (if correct completion needs going beyond the brief, ask instead of expanding the mandate). See references/review-and-land.md.

References

© amElnagdy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references) in skills/vibe-delegate of amElnagdy/delegate-skills.

  • SKILL.md
  • references/dispatch-and-poll.md
  • references/multi-task-queues.md
  • references/review-and-land.md
  • references/writing-the-brief.md
  • scripts/relay.mjs

Open the folder on GitHubat commit 8ef0210

Compare with similar skills

Vibe Delegate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vibe Delegate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Delegate this skillamElnagdy/delegate-skills2.3k—~1.6kAutomated safety check: PassMIT
Add ModelPipelex/pipelex942—~2.8kAutomated safety check: PassCustom licence
Vibe Textual UI Conventionsmistralai/mistral-vibe5.1k—~591Automated safety check: PassApache-2.0
Write Vibe Design Docmistralai/mistral-vibe5.1k—~3kAutomated safety check: PassApache-2.0
Liger Autopatchlinkedin/Liger-Kernel6.7k—~1.3kAutomated safety check: PassBSD-2-Clause
Write Vibe Testsmistralai/mistral-vibe5.1k—~1.2kAutomated safety check: PassApache-2.0

Similar skills

  • Add Model

    Pipelex/pipelex

    Add a new AI model to Pipelex's own inference configuration: the backend TOMLs in .pipelex/inference/backends/ (OpenAI, Azure, Anthropic, Bedrock, Google, Vertex, Mistral and the rest), the kit…

    942 GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Vibe Textual UI Conventions

    mistralai/mistral-vibe

    Official

    Conventions for building and styling Textual widgets and TCSS in the Mistral Vibe codebase: selectable lists, tool headers, theme variables and overflow.

    5.1k GitHub stars~591 tokensUpdated today
    DevelopmentAuto-check passed

  • Write Vibe Design Doc

    mistralai/mistral-vibe

    Official

    Create or update implementation-ready design proposals for Mistral Vibe under docs/design, including a bounded design-tree decision review before drafting.

    5.1k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed

  • Liger Autopatch

    linkedin/Liger-Kernel

    Adds Liger Kernel support for a new HuggingFace Transformers model, or modifies existing monkey-patching.

    6.7k GitHub stars~1.3k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Write Vibe Tests

    mistralai/mistral-vibe

    Official

    Guides writing or refactoring tests for the Mistral Vibe CLI agent so they check behavior through stable boundaries, like tool invocation or saved session shape, instead of internal calls.

    5.1k GitHub stars~1.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Hf Architecture Tikz

    yzlnew/infra-skills

    Draw Sebastian-Raschka-gallery-style TikZ architecture diagrams for any HuggingFace decoder-only LLM, with per-block parameter formulas and concrete numbers.

    149 GitHub stars~2k tokensUpdated 3 mo ago
    Documents & OfficeAuto-check passed

More from amElnagdy/delegate-skills

All 18 skills in this repo

  • Aider Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to Aider (aider) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~3k tokens
    Auto-check passed

  • Qoder Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Qoder CLI (qodercli) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check passed

  • Warp Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~2.6k tokens
    Auto-check passed

  • Agy Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Claude Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself.

    2.3k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Cline Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to the Cline coding agent CLI (cline) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Vibe Delegate

What does Vibe Delegate do?

Delegate a coding task to the Mistral Vibe CLI (vibe) as a background implementer, then review its diff and land it yourself. Vibe Delegate is an agent skill from amElnagdy/delegate-skills. Delegate a coding task to the Mistral Vibe CLI (vibe) as a background implementer, then review its diff and land it yourself.

When should I use Vibe Delegate?

Vibe Delegate fits situations like: 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 —.

How do I install Vibe Delegate in Claude Code?

Run `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -a claude-code`. Or copy the skill folder (skills/vibe-delegate in amElnagdy/delegate-skills) into .claude/skills/vibe-delegate in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Delegate in Codex?

Run `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -a codex`. Or copy the skill folder (skills/vibe-delegate in amElnagdy/delegate-skills) into .agents/skills/vibe-delegate in your project. Codex loads it when a task matches its description.

Can I use Vibe Delegate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amElnagdy/delegate-skills --skill vibe-delegate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-delegate, .gemini/skills/vibe-delegate, .github/skills/vibe-delegate and .opencode/skills/vibe-delegate in your project.

What does Vibe Delegate need to run?

Going by SKILL.md and its folder, Vibe Delegate needs JavaScript for the scripts in its folder, the command-line tools its instructions call (node and uv) and credentials named MISTRAL_API_KEY. Our summary lists: Node.js; A credential in MISTRAL_API_KEY.

Does Vibe Delegate access the network?

SKILL.md names 1 domain. As links in the text: docs.astral.sh. This is read from the text; nothing was executed.

Is Vibe Delegate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Vibe Delegate use?

Vibe Delegate is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vibe Delegate use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.

What are the alternatives to Vibe Delegate?

Skills that share tags, products or a category with Vibe Delegate: Add Model (Pipelex/pipelex, 942 stars), Vibe Textual UI Conventions (mistralai/mistral-vibe, 5.1k stars), Write Vibe Design Doc (mistralai/mistral-vibe, 5.1k stars) and Liger Autopatch (linkedin/Liger-Kernel, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Delegate?

amElnagdy (a GitHub user) maintains it in amElnagdy/delegate-skills, which has 2,347 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.

Source: amElnagdy/delegate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.