[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C45SDGR181SJY29MPQSSM8":3,"skill-same:01M6C45SDGR181SJY29MPQSSM8":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":12,"updatedAt":60,"install":61,"resources":74},"01M6C45SDGR181SJY29MPQSSM8","write-vibe-adr",null,"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\u002Fadr or AGENTS.md must be changed.","mistralai\u002Fmistral-vibe","mistralai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132372032?v=4","01M6C456ET86MBBTS4RMX0NDRS","Mistral","01M6C456K44X5W8TJX4T023KRV",5362,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002F.vibe\u002Fskills\u002Fwrite-vibe-adr\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,12,37,38,39,40,41,42,43],"adr","vibe","write vibe adr","write","new","design","when","review feedback","architecture decision","python cli","for","records","register","document","use","decision","feedback","architecture decision records","update","create","architecture","python","docs","cli","review","2026-11-10 10:12:30",false,"---\nname: write-vibe-adr\ndescription: 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\u002Fadr or AGENTS.md must be changed.\nmetadata:\n  display-name: Write Vibe ADR\n  short-description: Create architecture ADRs for Vibe\n  default-prompt: Use $write-vibe-adr to document a Vibe architecture decision and register it for agents.\n---\n\n# Write Vibe ADR\n\nVibe ADRs are concise, agent-facing architecture rules in `docs\u002Fadr\u002F`. Writing an ADR is a two-step process: write the document, then register it in the Architecture Decisions table in `AGENTS.md`.\n\n## When To Create An ADR\n\n- A design discussion creates a new architecture rule, constraint, or direction.\n- An existing convention is undocumented and caused a bug, review comment, or repeated confusion.\n- A pattern applies across a Vibe area or boundary, not just one file.\n- Future work should follow a direction that may differ from the current architecture.\n\nDo not create ADRs for one-off implementation choices, formatting rules, or behavior already enforced by linting.\n\n## Steps\n\n### 1. Confirm the scope\n\nUse one ADR when the decision is cohesive. Split ADRs when separate agents would need to read them for unrelated change areas.\n\nUse the Architecture Decisions table in `AGENTS.md` as the current topic\nindex. Ownership lives in `0002`, feature-module rules in `0018`, and the\nclient protocol boundary in `0009`. Keep implementation walkthroughs in\n`docs\u002Freference\u002F` and link them from the concise decision.\n\n### 2. Determine the next number\n\n```bash\nls docs\u002Fadr\u002F\n```\n\nUse the next sequential number, zero-padded to 4 digits: `NNNN-my-decision.md`.\nDo not reuse a number or rename an existing ADR solely to change its title.\n\n### 3. Write the ADR\n\nUse this format:\n\n```markdown\n# 0009 Decision Title\n\n## Decision\n\nWhat we decided. Include concrete rules and current-vs-aspirational direction when relevant.\n\n## Rationale\n\nWhy this decision exists. Name the tradeoff and any non-obvious consequences.\nMention a rejected alternative only when it helps explain the decision.\n\n## Agent Guidance\n\n- Concrete instructions an agent should follow while changing code.\n- Keep guidance task-oriented and easy to scan.\n\n## Flag To User When\n\n- Situations where an agent must stop and ask because current code or user request conflicts with the ADR direction.\n```\n\nKeep ADRs concise. Match the existing 20-50 line style. Do not add a status field.\nGive each rule one authoritative ADR; link to it rather than restating it.\nDecision states constraints, Agent Guidance gives their concrete application,\nand Flag To User When lists only topic-specific exceptions. Keep detailed\nimplementation mechanics in reference pages. When merging decisions, preserve\nthe old path with a short supersession notice and update the task index.\n\n### 4. Register in AGENTS.md\n\nAdd or update a row in the Architecture Decisions table:\n\n```markdown\n| \u003Ctask trigger> | [0009 Decision Title](docs\u002Fadr\u002F0009-my-decision.md) |\n```\n\nThe trigger text must describe what the agent is changing, not vague architecture language.\n\nGood triggers:\n\n- \"Adding a new delivery surface, protocol bridge, or UI-owned behavior\"\n- \"Changing tool args\u002Fresults, permissions, output limits, or adapters\"\n- \"Changing session transcript shape, metadata, resume, rewind, or migrations\"\n\nBad triggers:\n\n- \"Working on architecture\"\n- \"When relevant\"\n- \"Making decisions\"\n\nIf the ADR is not registered in `AGENTS.md`, agents will not reliably discover it.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Writing the ADR but not updating `AGENTS.md` | Always do both. |\n| Using vague trigger text | Name concrete code-change scenarios. |\n| Duplicating another ADR | Reference or update the existing ADR instead. |\n| Writing a human essay | Keep it short, directive, and agent-facing. |\n| Copying an implementation plan into the ADR | Keep only the durable rule and its consequences. |\n| Adding status fields | Vibe ADRs intentionally mix current and aspirational decisions without status. |\n","# Write Vibe ADR\n\nVibe ADRs are concise, agent-facing architecture rules in `docs\u002Fadr\u002F`. Writing an ADR is a two-step process: write the document, then register it in the Architecture Decisions table in `AGENTS.md`.\n\n## When To Create An ADR\n\n- A design discussion creates a new architecture rule, constraint, or direction.\n- An existing convention is undocumented and caused a bug, review comment, or repeated confusion.\n- A pattern applies across a Vibe area or boundary, not just one file.\n- Future work should follow a direction that may differ from the current architecture.\n\nDo not create ADRs for one-off implementation choices, formatting rules, or behavior already enforced by linting.\n\n## Steps\n\n### 1. Confirm the scope\n\nUse one ADR when the decision is cohesive. Split ADRs when separate agents would need to read them for unrelated change areas.\n\nUse the Architecture Decisions table in `AGENTS.md` as the current topic\nindex. Ownership lives in `0002`, feature-module rules in `0018`, and the\nclient protocol boundary in `0009`. Keep implementation walkthroughs in\n`docs\u002Freference\u002F` and link them from the concise decision.\n\n### 2. Determine the next number\n\n```bash\nls docs\u002Fadr\u002F\n```\n\nUse the next sequential number, zero-padded to 4 digits: `NNNN-my-decision.md`.\nDo not reuse a number or rename an existing ADR solely to change its title.\n\n### 3. Write the ADR\n\nUse this format:\n\n```markdown\n# 0009 Decision Title\n\n## Decision\n\nWhat we decided. Include concrete rules and current-vs-aspirational direction when relevant.\n\n## Rationale\n\nWhy this decision exists. Name the tradeoff and any non-obvious consequences.\nMention a rejected alternative only when it helps explain the decision.\n\n## Agent Guidance\n\n- Concrete instructions an agent should follow while changing code.\n- Keep guidance task-oriented and easy to scan.\n\n## Flag To User When\n\n- Situations where an agent must stop and ask because current code or user request conflicts with the ADR direction.\n```\n\nKeep ADRs concise. Match the existing 20-50 line style. Do not add a status field.\nGive each rule one authoritative ADR; link to it rather than restating it.\nDecision states constraints, Agent Guidance gives their concrete application,\nand Flag To User When lists only topic-specific exceptions. Keep detailed\nimplementation mechanics in reference pages. When merging decisions, preserve\nthe old path with a short supersession notice and update the task index.\n\n### 4. Register in AGENTS.md\n\nAdd or update a row in the Architecture Decisions table:\n\n```markdown\n| \u003Ctask trigger> | [0009 Decision Title](docs\u002Fadr\u002F0009-my-decision.md) |\n```\n\nThe trigger text must describe what the agent is changing, not vague architecture language.\n\nGood triggers:\n\n- \"Adding a new delivery surface, protocol bridge, or UI-owned behavior\"\n- \"Changing tool args\u002Fresults, permissions, output limits, or adapters\"\n- \"Changing session transcript shape, metadata, resume, rewind, or migrations\"\n\nBad triggers:\n\n- \"Working on architecture\"\n- \"When relevant\"\n- \"Making decisions\"\n\nIf the ADR is not registered in `AGENTS.md`, agents will not reliably discover it.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Writing the ADR but not updating `AGENTS.md` | Always do both. |\n| Using vague trigger text | Name concrete code-change scenarios. |\n| Duplicating another ADR | Reference or update the existing ADR instead. |\n| Writing a human essay | Keep it short, directive, and agent-facing. |\n| Copying an implementation plan into the ADR | Keep only the durable rule and its consequences. |\n| Adding status fields | Vibe ADRs intentionally mix current and aspirational decisions without status. |\n",{"name":5,"metadata":49,"description":7},{"display-name":50,"default-prompt":51,"short-description":52},"Write Vibe ADR","Use $write-vibe-adr to document a Vibe architecture decision and register it for agents.","Create architecture ADRs for Vibe","main","338ad4bf0f73c4dd879d667cf7ab011555ae1751",".vibe\u002Fskills\u002Fwrite-vibe-adr",794,"https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe","https:\u002F\u002Fgithub.com\u002Fmistralai","mistral.ai","2026-11-11 00:56:57",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add mistralai\u002Fmistral-vibe --skill write-vibe-adr",{"tool":67,"command":68},"bunx","bunx skills add mistralai\u002Fmistral-vibe --skill write-vibe-adr",{"tool":70,"command":71},"pnpm","pnpm dlx skills add mistralai\u002Fmistral-vibe --skill write-vibe-adr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002F.vibe\u002Fskills\u002Fwrite-vibe-adr\u002FSKILL.md",true,[],[76,105,126,150,170,190],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":87,"publishedAt":44},"01M71709JBNSMH1MJ71NRGRBFM","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.","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fplugins\u002Fbuiltins\u002Fvibe\u002Fskills\u002Fimport\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[78,88,89,90,91,92,93,94,95,96,42,97,98,99,25,100,101,102,103,104],"setup","file","configuration","mcp servers","servers","plugins","commands","instructions","opencode","codex","permissions","code","load","MCP","reuse","hooks","switch",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":44},"01M6C46D6AE5JDVJTFTXH9RZ5Q","worktree","Create, reuse, and clean up git worktrees under $VIBE_HOME\u002Fworktrees. Use when the user wants to work in an isolated git worktree, create a worktree for a task, or list\u002Fremove existing worktrees.","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fplugins\u002Fbuiltins\u002Fvibe\u002Fskills\u002Fworktree\u002FSKILL.md",[],[107,112,113,29,114,115,116,117,118,33,119,120,121,38,122,123,124,25,125,102],"clean","worktrees","home","up","user","git worktrees","remove","git worktree","list","work","git","true","task","Existing",{"skillNo":127,"name":20,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":44},"01M6C46A11K3H7D6F7ATSBRYKJ","Authoritative reference for Mistral Vibe — the CLI agent you (the model) are running inside.\n\nLOAD when the user:\n- asks anything about Vibe itself, even by indirect name (\"this CLI\", \"this tool\", \"you\");\n- wants to change, inspect, or reset their setup;\n- asks why the agent did or did not act;\n- asks how to make the CLI do X, where X lives, or what a flag\u002Fcommand\u002Fsetting does;\n- asks any meta question about your own behavior;\n- is unsure whether a command, flag, env var, or file is in scope — this skill is the source of truth.\n\nSCOPE: config under `~\u002F.vibe\u002F` and project-local `.vibe\u002F`; `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.","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fplugins\u002Fbuiltins\u002Fvibe\u002Fskills\u002Fvibe\u002FSKILL.md",[131],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[20,133,134,29,135,136,137,138,139,140,141,142,143,144,145,146,147,101,148,149],"themes","you","do","act","log","Meta","inspect","project","subagents","config","why","how","command","change","logs","question","local",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":44},"01M6C467E56WQ8PXEZT1Q0VP23","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.","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fplugins\u002Fbuiltins\u002Fvibe\u002Fskills\u002Fskill-creator\u002FSKILL.md",[156],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[158,159,160,161,162,20,163,164,134,165,100,166,167,168,169],"creator","skill creator","plan","flow","support","add","it","frontmatter","files","permission","directory","discovery",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":177,"publishedAt":44},"01M6C464DMPVA3RTXG0RGGZB3T","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.","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fplugins\u002Fbuiltins\u002Fvibe\u002Fskills\u002Fcreate-plugin\u002FSKILL.md",[176],{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},[38,178,179,116,92,180,181,182,25,183,29,184,185,12,33,186,101,91,187,93,103,188,189],"plugin","create plugin","with","extensions","author","agent plugins","connectors","scaffold","package","knowledge","format","libraries",{"skillNo":191,"name":192,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":44},"01M6C4620AT7K4999KR0YY86KH","prompts","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fcore\u002Ftools\u002Fbuiltins\u002Fprompts\u002Fskill.md",[],[192]]