Vibe Plugin Scaffolding
Scaffolds a Mistral Vibe plugin with skills, MCP servers, hooks and connectors.
Install
npx skills add mistralai/mistral-vibe --skill create-plugin -g -a claude-code -y- Repository
- mistralai/mistral-vibe5.3k
- Category
- AI and agents
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Create a Vibe plugin package, the Agent Plugins 1.0 format with optional Vibe extensions for skills, MCP servers, hooks, knowledge, agents, libraries, and connectors. Use when the user wants to create, scaffold, or author a plugin for Mistral Vibe.
Create a Vibe Plugin
A plugin is a directory containing a plugin.json manifest (Agent Plugins 1.0
schema) plus optional component directories and config files. Vibe discovers
plugins under .vibe/plugins/ (project scope, requires trusted folder) and
~/.vibe/plugins/ (user global).
Plugin discovery locations
| Scope | Path | When |
|---|---|---|
| Project | <project>/.vibe/plugins/<name>/ | trusted folder only |
| User global | ~/.vibe/plugins/<name>/ | always |
Each subdirectory under a plugins root is one plugin package. The first match wins: project plugins take precedence over user plugins with the same name.
Plugin directory structure
my-plugin/
plugin.json # required, Agent Plugins 1.0 manifest
mcp.json # optional, MCP server definitions
libraries.json # optional, Node/Python library dependencies
connectors.json # optional, managed connector requirements
skills/ # optional, one subdirectory per skill
my-skill/
SKILL.md
ai.mistral.vibe/ # optional, Vibe-specific extensions
hooks.toml # Vibe extension only
knowledge/ # one subdirectory per knowledge folder
topic-name/
KNOWLEDGE.md
agents/ # one .toml per subagent
researcher.toml
INSTRUCTIONS.md # optional plugin-wide instructions (not loaded)
Step 1, plugin.json (required)
The manifest is a JSON file with $schema and name as required fields.
