Automated summary
Configuration reference for customizing the Mistral Vibe CLI coding agent: the TOML .vibe/ tree, AGENTS.md instructions, native skills, custom agents and subagents, MCP servers, and experimental hooks.
Strengths
- Explicit table separating native capabilities (skills, agents, MCP) from partial ones (hooks, rules, commands)
- Gives exact file paths and states that config is TOML under .vibe/ and that instructions live in AGENTS.md, not CLAUDE.md
- Flags concrete gotchas: the trusted-folders gate, no MCP OAuth yet, and hooks limited to the post-agent-turn lifecycle
- Clearly separates the three Mistral surfaces so you don't configure the wrong one
Limitations
- Covers only the Mistral Vibe CLI; Mistral Code (IDE plugin) and Le Chat are explicitly out of scope
- Snapshot dated 2026-06-02, so version and schema details may drift from current docs
- Describes the expected layout but ships no ready-to-copy configuration files
Use it when setting up or auditing a Mistral Vibe CLI integration for a project (AGENTS.md, .vibe/, skills, agents, MCP).
Don't use it to configure Claude Code, Cursor, or another agent, nor for the Mistral Code IDE plugin or Le Chat.
Security analysis
SafeThis is a reference document describing configuration files, paths, and integration steps for the Mistral Vibe CLI. It contains no executable payloads, destructive commands, secret exfiltration, or obfuscated code. The only commands shown are harmless verification commands such as Test-Path and version checks. No declared tools are required.
No concerns found
How this analysis is madeExamples
Set up Mistral Vibe CLI for this repository: write the project AGENTS.md, a .vibe/config.toml overlay, and a project skill under .vibe/skills/ — tell me exactly which files go where.Does Mistral Vibe support pre-tool hooks or .mdc-style scoped rules? Tell me what is actually native, what is experimental, and what I cannot wire up.Create a .vibe/agents/reviewer.toml subagent profile and register a stdio MCP server in .vibe/config.toml, using the Mistral Vibe config format.name: g-skl-platform-mistral description: Authoritative reference for Mistral Vibe CLI (mistral-vibe) coding agent customization in gald3r projects. Covers the .vibe/ config tree (TOML), AGENTS.md instructions, native Agent-Skills SKILL.md, native custom agents + subagents, MCP servers, experimental hooks, and honest capability boundaries. crawl_max_age_days: 14 vault_doc_path: research/platforms/mistral/ vault_docs_url: https://docs.mistral.ai/mistral-vibe/terminal docs_url: https://docs.mistral.ai/mistral-vibe/terminal docs_url_secondary:
- https://docs.mistral.ai/vibe/code/cli/configuration
- https://docs.mistral.ai/vibe/code/cli/skills
- https://docs.mistral.ai/vibe/code/cli/agents
- https://docs.mistral.ai/vibe/code/cli/mcp-servers
- https://github.com/mistralai/mistral-vibe last_doc_scan: 2026-06-02 capability_status: hooks: "⚠️ experimental post-agent-turn lifecycle only (v2.9.0); no schema/file location; no pre-tool/session-start/pre-commit — cannot wire gald3r hooks" rules: "⚠️ AGENTS.md layered injection (+ optional custom system prompt via prompts/<id>.md); no scoped .mdc/glob rule system" skills: "✅ native Agent Skills (agentskills.io SKILL.md) in ~/.vibe/skills, ./.vibe/skills, ./.agents/skills + skill_paths" commands: "⚠️ slash commands only via skills (user-invocable: true → /skill-name); no command-file directory" agents: "✅ native custom agents + subagents (.vibe/agents/*.toml; vibe --agent; agent_type=subagent)" mcp: "✅ native — config.toml [[mcp_servers]] (http/streamable-http/stdio); no OAuth yet" token_budget: low subsystem_memberships: [PLATFORM_INTEGRATION]
g-skl-platform-mistral
Activate for: setting up gald3r with Mistral Vibe CLI (mistral-vibe), authoring Mistral project
instructions / skills / agents, or verifying the Mistral gald3r integration.
Full 9-section breakdown + evidence URLs in
PLATFORM_SPEC.md(this folder). Status: ⚠️ partial parity. Native: skills, agents/subagents, MCP. Partial: hooks (experimental post-agent-turn only), rules (AGENTS.mdinjection, no.mdcscoping), commands (skill-provided only). Vibe readsAGENTS.md(NOTCLAUDE.md); config is TOML under.vibe/(no.mistral/, no YAML). (Verified 2026-06-02 against docs.mistral.ai + github.com/mistralai/mistral-vibe; latest observed v2.13.0.)
1. Platform Overview
"Mistral" coding is three products — gald3r targets only the config-driven one:
| Surface | What it is | gald3r config target? |
|---|---|---|
| Mistral Vibe CLI | Open-source terminal coding agent (mistral-vibe) | ✅ Yes — reads .vibe/ + AGENTS.md |
| Mistral Code | JetBrains/VSCode IDE plugin (enterprise bundle) | ❌ Closed plugin; no config files |
| Le Chat | Web/app chat with MCP connectors + memories | ❌ Not a file-config surface |
- Config root:
.vibe/(user~/.vibe/, project./.vibe/) — TOML, not YAML. There is no.mistral/directory. - Instructions:
AGENTS.md(the same cross-platform standard gald3r already uses) — notCLAUDE.md. - Trusted-folders gate: project
.vibe/config loads only when the working directory is trusted (trusted_folders.toml).
2. Config Layout
~/.vibe/ ← user-global
├── config.toml ← models, providers, tools, [[mcp_servers]], enabled_skills (TOML)
├── .env ← API keys
├── AGENTS.md ← user-level instructions
├── agents/<name>.toml ← custom agent / subagent profiles (TOML)
├── prompts/<id>.md ← custom system prompts (system_prompt_id)
└── skills/<name>/SKILL.md ← user-level skills (agentskills.io)
<project-root>/
├── AGENTS.md ← project instructions (override user-level; closer files win)
└── .vibe/
├── config.toml ← project overlay
├── skills/<name>/SKILL.md ← project skills (also ./.agents/skills/)
├── agents/<name>.toml ← project agent / subagent profiles
└── prompts/<id>.md
Resolution: project paths layer over user paths; files closer to the working directory win. Project
.vibe/ loads only in trusted folders.
3. gald3r Integration
Cheapest high-value install: ship gald3r's AGENTS.md — Vibe consumes it directly with no
transformation. gald3r skills (g-skl-*/SKILL.md) load natively (agentskills.io); native agents/
subagents exist but need markdown→TOML conversion.
# AGENTS.md (gald3r section)
## Task Workflow
Before any implementation:
1. Read .gald3r/TASKS.md for active tasks
2. Read .gald3r/tasks/task{id}_*.md for task details
3. Check .gald3r/CONSTRAINTS.md for architectural limits
## Commit Format
feat(T{id}): description
fix(BUG-{id}): description
## Bug Discovery
Pre-existing bugs: document in .gald3r/BUGS.md — never silently ignore.
MCP servers (optional) go in .vibe/config.toml:
[[mcp_servers]]
name = "my_http_server"
transport = "http" # http | streamable-http | stdio
url = "http://localhost:8000"
startup_timeout_sec = 15
tool_timeout_sec = 120
The parity pipeline (
platform_parity_sync.ps1) does not currently write.vibe/. There is no automated Mistral install path yet — integration is manualAGENTS.mdauthoring today.
Verify
Test-Path AGENTS.md
Test-Path .vibe
mistral-vibe --version # or: vibe --version (confirm CLI install)
4. Common Pitfalls
- Vibe reads
AGENTS.md, NOTCLAUDE.md. Config is.vibe/config.toml(TOML), NOT.mistral/config.yaml(that path is fictional). - "Mistral Code" (IDE plugin) and "Le Chat" do not read these files — only Vibe CLI does.
- Project
.vibe/config (skills/agents/prompts/hooks) loads only in trusted folders (trusted_folders.toml). - Slash commands are skill-provided only (
user-invocable: true) — there is no command-file directory like.cursor/commands/. - Vibe skill frontmatter expects
allowed-tools/user-invocable; gald3r skills emitsubsystem_memberships/token_budget(unknown keys ignored — light adaptation). - Keep API keys in
~/.vibe/.env/ environment variables, never in committedconfig.toml.
5. Capability Summary
| Feature | Status | Notes |
|---|---|---|
| Skills (g-skl-*/SKILL.md) | ✅ | native agentskills.io; ~/.vibe/skills, ./.vibe/skills, ./.agents/skills, skill_paths |
| Agents (g-agnt-*.md) | ✅ | native custom agents + subagents .vibe/agents/*.toml (vibe --agent; agent_type=subagent); needs md→TOML port |
| MCP | ✅ | config.toml [[mcp_servers]] (http / streamable-http / stdio); namespaced {server}_{tool}; no OAuth yet |
| Hooks (g-hk-*.ps1) | ⚠️ | experimental post-agent-turn only (v2.9.0); no schema/file location; no pre-tool/session-start/pre-commit |
| Rules (g-rl-*) | ⚠️ | AGENTS.md layered injection (+ optional custom system prompt); no scoped .mdc/glob rules |
| Commands (@g-*) | ⚠️ | slash commands only via skills (user-invocable: true → /skill-name); no command-file dir |
6. Known Gaps
Ground-truth hook events (T1538/T1554): mistral ships an experimental
.vibe/hook surface (Type:experimental) — a single post-agent-turn lifecycle point (v2.9.0, 2026-04-28) — but publishes no event list, file location, or schema, so the wiring is undocumented. The authoritative, machine-readable statement of this — the (currently undocumented) event list and how gald3r hook behaviors must run until it is verified (manually, via rules text, or via gitcore.hooksPath) — lives inPLATFORM_SPEC.md->## Hook System. Reference that block rather than re-listing hook details here. The gald3rg-hk-*.ps1wiring for mistral is [STUB] / unverified — do not fabricate an event-to-hook mapping. Last verified against platform version: mistral v2.13.0 (docs crawllast_doc_scan: 2026-06-02). Re-verify the event names inPLATFORM_SPEC.md## Hook Systemon the next@g-platform-scan-docs mistral.
Honest boundaries vs. the Cursor reference (full detail in PLATFORM_SPEC.md §1–§9):
- Hooks ⚠️: experimental post-agent-turn lifecycle only (v2.9.0); no published event list or
schema, and no pre-tool/session-start/pre-commit — gald3r's
g-hk-*.ps1+hooks.jsoncannot be ported until Mistral documents the format. (issue #250 CLOSED unimplemented; #531 OPEN) - Rules ⚠️: no
.mdcscoped-rule system; gald3r'sg-rl-*rules collapse into a singleAGENTS.mdblob (noglobs, no per-rule on-demand loading); optional custom system prompt viaprompts/<id>.md+system_prompt_id. - Commands ⚠️: slash commands are skill-provided only (
user-invocable: true) — no command-file directory like.cursor/commands/; gald3r's command files have no native landing zone. - Agents ✅ (with caveat): native custom agents + subagents, but Vibe agents are TOML behavior
profiles, not gald3r's markdown agents — a port needs markdown→TOML conversion;
safetyis visual-only (not enforcement). - Skills ✅ (with caveat): native Agent Skills spec + folder-per-skill
SKILL.mdmatches, but Vibe expectsallowed-tools/user-invocablekeys gald3r skills don't emit (light adaptation). - MCP ✅ (with caveat): native
[[mcp_servers]], but the CLI does not yet support OAuth MCP servers. - No install automation:
platform_parity_sync.ps1has no.vibe/writer — future work.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mistral-vibe-cli-platform-mrzxupqq/download' --output '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md.part' && mv '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md.part' '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md' && test -s '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/g-skl-platform-mistral' && cp -R '.skill-downloads/mistral-vibe-cli-platform-mrzxupqq' '.claude/skills/g-skl-platform-mistral'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/mistral-vibe-cli-platform-mrzxupqq'openskills read 'mistral-vibe-cli-platform-mrzxupqq'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/mistral-vibe-cli-platform-mrzxupqq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.