Agent skill

Vibe Delegate

by sickn33 in sickn33/agentic-awesome-skills

Delegate coding tasks to the Mistral Vibe CLI (vibe) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

MITAuto-check passed

Install Vibe Delegate

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill vibe-delegate -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-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/sickn33/agentic-awesome-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
47k
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
763 words
Files
5 (incl. references)
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Delegate coding tasks to the Mistral Vibe CLI (vibe) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

  • Works in 5 steps: Write the brief → Dispatch → Wait for completion → …
  • Explicitly requests it
  • SKILL.md covers When to Use, When NOT to use this, Prerequisites (check once) and The loop, plus 4 more sections
  • Calls node and uv; needs MISTRAL_API_KEY

What it does

Vibe Delegate is an agent skill from sickn33/agentic-awesome-skills. Delegate coding tasks to the Mistral Vibe CLI (vibe) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

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

It works with Mistral AI. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Explicitly requests it
  • While the orchestrator retains review and landing responsibility

Example prompts

  • “/vibe-delegate”

Requirements

  • 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 b84d35a. 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

    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
    • github.com

    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.8k tokens when it runs, and up to ~6.8k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 763 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 763 words, ~1,755 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-delegate/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
vibe-delegate
description
Delegate coding tasks to the Mistral Vibe CLI (`vibe`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.
risk
critical
category
agent-orchestration
source
https://github.com/amElnagdy/delegate-skills
source_repo
amElnagdy/delegate-skills
source_type
community
date_added
2026-08-26
license
MIT
license_source
https://github.com/amElnagdy/delegate-skills/blob/master/LICENSE
metadata.version
0.5.0

Vibe Delegate

When to Use

  • You want to delegate a bounded coding task to a separate vibe implementer (Mistral Vibe) and then review its diff yourself.
  • The user explicitly asked for delegation to this implementer.

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 (308 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

Limitations

  • Docs-only import — executable scripts/relay.mjs not included; see upstream for full runtime. Requires vibe CLI, Node 18+, git.
  • Relay never commits — it only returns structured result JSON; you review and land the commit.

Adapted from amElnagdy/delegate-skills (MIT) — docs-only, runtime not bundled.

© sickn33, 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 4 other files (references) in skills/vibe-delegate of sickn33/agentic-awesome-skills.

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

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

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 skillsickn33/agentic-awesome-skills47k1 repos~1.8kAutomated safety check: PassMIT
Higress Openclaw Integrationhigress-group/higress9.5k—~2.5kAutomated safety check: PassApache-2.0
Embeddings via 9Routerdecolua/9router31k—~604Automated safety check: PassMIT
Liger Autopatchlinkedin/Liger-Kernel6.7k—~1.3kAutomated safety check: PassBSD-2-Clause
AI SDK Developmenttrypostit/trypost6911 repos~3.5kAutomated safety check: PassMIT
Mistral Vibe Plugin Creatormistralai/mistral-vibe5.1k—~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • Higress Openclaw Integration

    higress-group/higress

    Deploy and configure Higress AI Gateway for OpenClaw integration.

    9.5k GitHub stars~2.5k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Embeddings via 9Router

    decolua/9router

    Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.

    31k GitHub stars~604 tokensUpdated yesterday
    AI & LLM EngineeringAuto-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
  • AI SDK Development

    trypostit/trypost

    TRIGGER when working with ai-sdk which is Laravel official first-party AI SDK.

    691 GitHub starsUsed in 1 repo~3.5k tokens
    AI & LLM EngineeringAuto-check passed
  • Mistral Vibe Plugin Creator

    mistralai/mistral-vibe

    Official

    Shows how to build a Vibe plugin package in the Agent Plugins 1.0 format, with a plugin.json manifest and optional skills, MCP servers, hooks and other components.

    5.1k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Liger Kernel Dev

    linkedin/Liger-Kernel

    Develops production-ready Triton kernels for Liger Kernel. An agent skill from linkedin/Liger-Kernel.

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

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Questions about Vibe Delegate

What does Vibe Delegate do?

Delegate coding tasks to the Mistral Vibe CLI (vibe) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility. Vibe Delegate is an agent skill from sickn33/agentic-awesome-skills. Delegate coding tasks to the Mistral Vibe CLI (vibe) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.

When should I use Vibe Delegate?

Vibe Delegate fits situations like: explicitly requests it; while the orchestrator retains review and landing responsibility.

How do I install Vibe Delegate in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill vibe-delegate -a claude-code`. Or copy the skill folder (skills/vibe-delegate in sickn33/agentic-awesome-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 sickn33/agentic-awesome-skills --skill vibe-delegate -a codex`. Or copy the skill folder (skills/vibe-delegate in sickn33/agentic-awesome-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 sickn33/agentic-awesome-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 the command-line tools its instructions call (node and uv) and credentials named MISTRAL_API_KEY. Our summary lists: A credential in MISTRAL_API_KEY.

Does Vibe Delegate access the network?

SKILL.md names 2 domains. As links in the text: docs.astral.sh and github.com. 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. Review the folder before installing.

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.8k tokens (SKILL.md is roughly 7k 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: Higress Openclaw Integration (higress-group/higress, 9.5k stars), Embeddings via 9Router (decolua/9router, 31k stars), Liger Autopatch (linkedin/Liger-Kernel, 6.7k stars) and AI SDK Development (trypostit/trypost, 691 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Delegate?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

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