import
Import the user's setup from other coding CLIs (Claude Code, Codex, OpenCode) into Vibe — instructions, skills, subagents, commands, hooks, MCP servers, permissions, and plugins. Load when the user wants to switch to Vibe, import or reuse another CLI's configuration, or asks whether a file from another CLI works in Vibe.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 5.4k
- Forks
- 795
01 前言 Front Matter
- name
- import
- description
- Import the user's setup from other coding CLIs (Claude Code, Codex, OpenCode) into Vibe — instructions, skills, subagents, commands, hooks, MCP servers, permissions, and plugins. Load when the user wants to switch to Vibe, import or reuse another CLI's configuration, or asks whether a file from another CLI works in Vibe.
03 SKILL.md 正文
Import From Other CLIs
Translate the user's Claude Code, Codex or OpenCode setup into Vibe and write
what they approve. This skill does not explain how those CLIs work: learn it
from their files and official docs. Learn Vibe's formats from the vibe:vibe
skill; load it first. Do not guess.
Where to look
| CLI | Config folders and files | Docs index |
|---|---|---|
| Claude Code | ~/.claude/, ~/.claude.json, CLAUDE.md, .claude/, .mcp.json |
https://code.claude.com/docs/llms.txt |
| Codex | $CODEX_HOME or ~/.codex/, .codex/ |
https://developers.openai.com/codex/llms.txt |
| OpenCode | ~/.config/opencode/, opencode.json(c), .opencode/ |
https://opencode.ai/llms.txt |
Fetch the docs index, then the page for each kind of item you found (settings, memory or instructions, skills, subagents, commands, hooks, MCP, permissions, plugins). Docs describe the latest version; when they disagree with the user's files, trust the files.
Steps
- Scan the paths above in the home directory and the current project.
Skip missing ones. Also read Vibe's config (
~/.vibe/,.vibe/) so you never duplicate or overwrite an item. - Learn. For each kind of item found, read the source CLI's doc page and
the matching
vibe:vibesection. Note what has no Vibe equivalent. - Plan. Show one table: item, source, Vibe target, status (
ready,changed,not portable), and a reason for anything notready. Home items go to~/.vibe/, project items to.vibe/(trusted folder only). Wait for approval. - Write the approved items. Back up any Vibe file before editing it. Never edit the other CLI's files without asking.
- Check. Ask the user to restart Vibe (hooks and agents load only at
startup,
/reloadis not enough), read the Warnings box, and look for failed servers in/mcp. Fix what they report. - Report what was imported, what changed on the way, and what was left behind and why.
Rules
- Never weaken a guard. A translated permission or hook must block at
least what the original blocked, under every Vibe agent. If you cannot show
it does, mark it
not portable. - Never copy secrets. Leave placeholders the user fills in. Never read
.envfiles. - Show every command a hook or MCP stdio server will run before writing it.
- Test every hook script with a sample Vibe payload on stdin before registering it.
- Reuse before copying.
AGENTS.mdand.agents/skills/are already shared. Pointskill_pathsat other skill folders when their skills are valid in Vibe. - Say when you don't know. If neither the docs nor
vibe:vibesettle a mapping, mark the itemnot portableand explain why.
04 同仓库更多 Skills
worktree
Create, reuse, and clean up git worktrees under $VIBE_HOME/worktrees. Use when the user wants to work in an isolated git worktree, create a worktree for a task, or list/remove existing worktrees.
vibe
Authoritative reference for Mistral Vibe — the CLI agent you (the model) are running inside. LOAD when the user: - asks anything about Vibe itself, even by indirect name ("this CLI", "this tool", "you"); - wants to change, inspect, or reset their setup; - asks why the agent did or did not act; - asks how to make the CLI do X, where X lives, or what a flag/command/setting does; - asks any meta question about your own behavior; - is unsure whether a command, flag, env var, or file is in scope — this skill is the source of truth. SCOPE: config under `~/.vibe/` and project-local `.vibe/`; `VIBE_*` and `LOG_*` env vars; models and providers; agents and subagents; skills; tools and their permission model; every slash command and CLI flag; hooks; MCP servers; connectors; plugins; trusted folders; `@`-file mentions; logs; themes; voice.
skill-creator
Load this skill before creating, updating, or deleting a Vibe skill, or whenever you plan to add or modify SKILL.md files under a skills directory. It explains Vibe's SKILL.md frontmatter, discovery order, support files, and the permission flow.
create-plugin
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.
prompts
暂无简介
write-vibe-tests
Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports/adapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests/ for vibe/core, vibe/app_server, vibe/acp, tools, config, sessions, skills, hooks, MCP, or setup.