Official agent skill

Write Vibe ADR

Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table.

OfficialApache-2.0Auto-check passedDevelopment

Install Write Vibe ADR

skills CLI

$ npx skills add mistralai/mistral-vibe --skill write-vibe-adr -a claude-code

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

GitHub CLI

$ gh skill install mistralai/mistral-vibe write-vibe-adr --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/mistralai/mistral-vibe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.vibe/skills/write-vibe-adr .claude/skills/write-vibe-adr && 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/

Paste into Claude Code

Install the "write-vibe-adr" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr into .claude/skills/write-vibe-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-vibe-adr", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add mistralai/mistral-vibe --skill write-vibe-adr -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mistralai/mistral-vibe write-vibe-adr --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.vibe/skills/write-vibe-adr .agents/skills/write-vibe-adr && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "write-vibe-adr" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr into .agents/skills/write-vibe-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-vibe-adr", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mistralai/mistral-vibe --skill write-vibe-adr -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mistralai/mistral-vibe write-vibe-adr --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.vibe/skills/write-vibe-adr .cursor/skills/write-vibe-adr && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "write-vibe-adr" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr into .cursor/skills/write-vibe-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-vibe-adr", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/mistralai/mistral-vibe.git --path .vibe/skills/write-vibe-adr

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mistralai/mistral-vibe --skill write-vibe-adr -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mistralai/mistral-vibe write-vibe-adr --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.vibe/skills/write-vibe-adr .gemini/skills/write-vibe-adr && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "write-vibe-adr" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr into .gemini/skills/write-vibe-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-vibe-adr", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install mistralai/mistral-vibe write-vibe-adr

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add mistralai/mistral-vibe --skill write-vibe-adr -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .github/skills && cp -r skills-src/.vibe/skills/write-vibe-adr .github/skills/write-vibe-adr && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "write-vibe-adr" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr into .github/skills/write-vibe-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-vibe-adr", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mistralai/mistral-vibe --skill write-vibe-adr -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mistralai/mistral-vibe write-vibe-adr --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mistralai/mistral-vibe.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.vibe/skills/write-vibe-adr .opencode/skills/write-vibe-adr && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "write-vibe-adr" agent skill from https://github.com/mistralai/mistral-vibe/tree/main/.vibe/skills/write-vibe-adr into .opencode/skills/write-vibe-adr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-vibe-adr", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: write-vibe-adr
GitHub stars: 5.1k
Token cost: ~942 tokens
SKILL.md length: 350 words
Files: 1
Skills in repo: 14
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table.

Works in 4 steps: Confirm the scope → Determine the next number → Write the ADR → …
A design discussion creates a new architecture rule or direction
SKILL.md covers When To Create An ADR, Steps and Common Mistakes
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill writes or updates Architecture Decision Records for the Mistral Vibe Python CLI. Vibe ADRs are short, agent-facing architecture rules in docs/adr/, and writing one takes two steps: write the document, then register it in the Architecture Decisions table in AGENTS.md so agents can find it. An ADR is warranted when a design discussion creates a new rule or direction, an undocumented convention caused a bug or repeated confusion, or a pattern spans a whole area; it is not for one-off implementation choices, formatting or anything linting already enforces.

The steps are to confirm scope, using one ADR for a cohesive decision and several when separate agents need them for unrelated changes, after checking the existing topics; take the next four-digit number from the directory listing; write the ADR in the existing 20 to 50 line style with no status field; and add a table row whose trigger names the concrete change an agent would be making, not vague phrases like working on architecture. Common mistakes are forgetting AGENTS.md, vague triggers and duplicating another ADR.

When your agent uses it

A design discussion creates a new architecture rule or direction
An undocumented convention caused a bug or repeated review comments
Registering a new ADR in the AGENTS.md Architecture Decisions table
Updating existing architecture guidance in docs/adr

Example prompts

“Write an ADR for the rule we just agreed on that every tool must declare its permissions.”
“Add a new ADR about session transcripts and register it in AGENTS.md with a concrete trigger.”
“Our reviews keep flagging the config layering convention, so document it as an ADR.”

Requirements

A checkout of the Mistral Vibe repository with docs/adr and AGENTS.md

Workflow steps

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

Confirm the scope
Determine the next number
Write the ADR
Register in AGENTS.md

What it can do on your machine

Read from SKILL.md and the folder at commit 7cb9189. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Write Vibe ADR loads about 942 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 350 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~942

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 mistralai/mistral-vibe at commit 7cb9189, republished under its Apache-2.0 licence (© mistralai). 350 words, ~942 tokens.

Download SKILL.mdSave it as .claude/skills/write-vibe-adr/SKILL.md (or your agent's skills folder).

name: write-vibe-adr
description: Create or update Architecture Decision Records for the Mistral Vibe Python CLI. Use when a design discussion creates a new architectural constraint, when an undocumented convention causes confusion or review feedback, or when architecture guidance in docs/adr or AGENTS.md must be changed.
metadata.display-name: Write Vibe ADR
metadata.short-description: Create architecture ADRs for Vibe
metadata.default-prompt: Use $write-vibe-adr to document a Vibe architecture decision and register it for agents.

Write Vibe ADR

Vibe ADRs are concise, agent-facing architecture rules in docs/adr/. Writing an ADR is a two-step process: write the document, then register it in the Architecture Decisions table in AGENTS.md.

When To Create An ADR

A design discussion creates a new architecture rule, constraint, or direction.
An existing convention is undocumented and caused a bug, review comment, or repeated confusion.
A pattern applies across a Vibe area or boundary, not just one file.
Future work should follow a direction that may differ from the current architecture.

Do not create ADRs for one-off implementation choices, formatting rules, or behavior already enforced by linting.

Steps

1. Confirm the scope

Use one ADR when the decision is cohesive. Split ADRs when separate agents would need to read them for unrelated change areas.

Existing ADR topics:

0001 - architecture principles
0002 - core engine and delivery surfaces
0003 - event-driven agent loop
0004 - typed permissioned tools
0005 - layered configuration
0006 - local sessions
0007 - extension mechanisms
0008 - feature instrumentation

2. Determine the next number

bash

ls docs/adr/

Use the next sequential number, zero-padded to 4 digits: 0009-my-decision.md.

3. Write the ADR

Use this format:

markdown

# 0009 Decision Title

## Decision

What we decided. Include concrete rules and current-vs-aspirational direction when relevant.

## Rationale

Why this decision exists. Name the tradeoff and any non-obvious consequences.
Mention a rejected alternative only when it helps explain the decision.

## Agent Guidance

- Concrete instructions an agent should follow while changing code.
- Keep guidance task-oriented and easy to scan.

## Flag To User When

- Situations where an agent must stop and ask because current code or user request conflicts with the ADR direction.

Keep ADRs concise. Match the existing 20-50 line style. Do not add a status field.

Show full SKILL.md (150 more words)Show less

4. Register in AGENTS.md

Add or update a row in the Architecture Decisions table:

markdown

| <task trigger> | [0009 Decision Title](docs/adr/0009-my-decision.md) |

The trigger text must describe what the agent is changing, not vague architecture language.

Good triggers:

"Adding a new delivery surface, protocol bridge, or UI-owned behavior"
"Changing tool args/results, permissions, output limits, or adapters"
"Changing session transcript shape, metadata, resume, rewind, or migrations"

Bad triggers:

"Working on architecture"
"When relevant"
"Making decisions"

If the ADR is not registered in AGENTS.md, agents will not reliably discover it.

Common Mistakes

Mistake	Fix
Writing the ADR but not updating `AGENTS.md`	Always do both.
Using vague trigger text	Name concrete code-change scenarios.
Duplicating another ADR	Reference or update the existing ADR instead.
Writing a human essay	Keep it short, directive, and agent-facing.
Copying an implementation plan into the ADR	Keep only the durable rule and its consequences.
Adding status fields	Vibe ADRs intentionally mix current and aspirational decisions without status.

Files

Just SKILL.md in .vibe/skills/write-vibe-adr of mistralai/mistral-vibe.

Open the folder on GitHubat commit 7cb9189

Compare with similar skills

Write Vibe ADR 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.

Write Vibe ADR compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Write Vibe ADR this skillmistralai/mistral-vibe	5.1k	—	~942	Automated safety check: Pass	Apache-2.0	2 days ago
Docsbrickbots/PiFinder	250	—	~6.2k	Automated safety check: Pass	GPL-3.0	2 days ago
Adk Stylegoogle/adk-python	22k	—	~769	Automated safety check: Pass	Apache-2.0	today
Generating Documentationancoleman/ai-design-components	526	—	~3k	Automated safety check: Pass	MIT	10 mo ago
Research Initbrycewang-stanford/Auto-Empirical-Research-Skills	4.5k	—	~839	Automated safety check: Pass	Custom licence	4 days ago
Adk Sample Creatorgoogle/adk-python	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Docs
brickbots/PiFinder
Author and edit PiFinder's user-facing documentation in the project's house style.
250 GitHub stars~6.2k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Adk Style
google/adk-python
Official
Python style and codebase conventions for ADK (Agent Development Kit): private-by-default file visibility, imports, type hints, Pydantic v2 models, formatting, docstrings, logging, async I/O, file…
22k GitHub stars~769 tokensUpdated today
DevelopmentAuto-check passed
Generating Documentation
ancoleman/ai-design-components
Generate comprehensive technical documentation including API docs (OpenAPI/Swagger), code documentation (TypeDoc/Sphinx), documentation sites (Docusaurus/MkDocs), Architecture Decision Records…
526 GitHub stars~3k tokensUpdated 10 mo ago
DevelopmentAuto-check passed
Research Init
brycewang-stanford/Auto-Empirical-Research-Skills
Scaffold a new research project with full reproducibility infrastructure in R and/or Python.
4.5k GitHub stars~839 tokensUpdated 4 days ago
DevelopmentAuto-check passed
Adk Sample Creator
google/adk-python
Official
Creates a new sample agent in the ADK Python repository — the sample directory, its agent.py, and its README.md — following the conventions the existing samples already use.
22k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Crafting Effective Readmes
cumbucadev/cinemaempoa
A skill your agent uses when writing or improving README files.
146 GitHub starsUsed in 5 repos~669 tokens
DevelopmentAuto-check passed

More from mistralai/mistral-vibe

All 14 skills in this repo

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 2 days ago
Auto-check passed
Create Vibe Feature
mistralai/mistral-vibe
Official
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.
5.1k GitHub stars~1.2k tokensUpdated 2 days ago
Auto-check passed
Feature Analytics Instrumentation Planner
mistralai/mistral-vibe
Official
Plans which analytics events and properties a new feature needs, checks them against the existing event registry, and verifies them per environment.
5.1k GitHub stars~2.2k tokensUpdated 2 days ago
Auto-check passed
Vibe Worktree Manager
mistralai/mistral-vibe
Official
Creates, reuses and cleans up git worktrees under a shared vibe home directory, with per-repo buckets, claim records and dirty-state checks before removal.
5.1k GitHub stars~1.2k tokensUpdated 2 days ago
Auto-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 2 days ago
Auto-check passed
Mistral Vibe CLI Reference
mistralai/mistral-vibe
Official
Reference for Mistral Vibe, the CLI agent it runs inside: config files, env vars, agents, skills, tools, hooks and MCP servers, so the agent can explain and troubleshoot its own setup.
5.1k GitHub stars~14k tokensUpdated 2 days ago
Auto-check: notes

Works with

Python

Questions about Write Vibe ADR

What does Write Vibe ADR do?

Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table. This skill writes or updates Architecture Decision Records for the Mistral Vibe Python CLI.md so agents can find it.

When should I use Write Vibe ADR?

Write Vibe ADR fits situations like: A design discussion creates a new architecture rule or direction; an undocumented convention caused a bug or repeated review comments; registering a new ADR in the AGENTS.md Architecture Decisions table; updating existing architecture guidance in docs/adr.

How do I install Write Vibe ADR in Claude Code?

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

How do I install Write Vibe ADR in Codex?

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

Can I use Write Vibe ADR 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 mistralai/mistral-vibe --skill write-vibe-adr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-vibe-adr, .gemini/skills/write-vibe-adr, .github/skills/write-vibe-adr and .opencode/skills/write-vibe-adr in your project.

What does Write Vibe ADR need to run?

SKILL.md names no scripts, command-line tools or credentials: Write Vibe ADR is instructions for the agent only. Our summary lists: A checkout of the Mistral Vibe repository with docs/adr and AGENTS.md.

Does Write Vibe ADR access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Write Vibe ADR 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 Write Vibe ADR use?

Write Vibe ADR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write Vibe ADR use?

About 942 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Write Vibe ADR?

Skills that share tags, products or a category with Write Vibe ADR: Docs (brickbots/PiFinder, 250 stars), Adk Style (google/adk-python, 22k stars), Generating Documentation (ancoleman/ai-design-components, 526 stars) and Research Init (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write Vibe ADR?

mistralai (a GitHub organization, an official publisher) maintains it in mistralai/mistral-vibe, which has 5,085 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.

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

Install Write Vibe ADR

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Write Vibe ADR

When To Create An ADR

Steps

1. Confirm the scope

2. Determine the next number

3. Write the ADR

4. Register in AGENTS.md

Common Mistakes

Files

Compare with similar skills

Similar skills

More from mistralai/mistral-vibe

Related

Questions about Write Vibe ADR