[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C45KMR4BCE0PB0H9M2J2FW":3,"skill-same:01M6C45KMR4BCE0PB0H9M2J2FW":74},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":12,"updatedAt":59,"install":60,"resources":73},"01M6C45KMR4BCE0PB0H9M2J2FW","vibe-rust-tui",null,"Ratatui UI conventions for the Mistral Vibe Rust CLI (vibe\u002Fcli-rust). Use when adding or changing any screen, list, picker, footer hint, keyboard shortcut, list navigation, scrolling or mouse clicks, back\u002Fclose behavior, search field, selection highlight, color, or onboarding\u002Fdialog copy in the Rust TUI.","mistralai\u002Fmistral-vibe","mistralai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F132372032?v=4","01M6C456ET86MBBTS4RMX0NDRS","Mistral","01M6C456K44X5W8TJX4T023KRV",5376,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvibe-rust-tui\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,12,40,41,42],"rust","tui","vibe rust tui","vibe","when","cli","hint","for","shortcut","color","close","screen","keyboard","back","selection","use","cursor","behavior","list","dialog","ratatui","ui","search","onboarding","2026-11-10 10:12:30",false,"---\nname: vibe-rust-tui\ndescription: Ratatui UI conventions for the Mistral Vibe Rust CLI (vibe\u002Fcli-rust). Use when adding or changing any screen, list, picker, footer hint, keyboard shortcut, list navigation, scrolling or mouse clicks, back\u002Fclose behavior, search field, selection highlight, color, or onboarding\u002Fdialog copy in the Rust TUI.\nmetadata:\n  display-name: Vibe Rust TUI\n  short-description: Hint, keyboard, navigation, mouse, search, list-cursor and color conventions for the Rust TUI\n  default-prompt: Use $vibe-rust-tui to follow the Rust TUI hint, keyboard, navigation, search, list-cursor and color conventions.\n---\n\n# Vibe Rust TUI\n\nUI conventions for `vibe\u002Fcli-rust\u002F`. Every screen follows them so the TUI reads as one product. Local code rules, scenarios and goldens live in `vibe\u002Fcli-rust\u002FAGENTS.md` and `client-e2e\u002FAGENTS.md`.\n\n## Shortcut hints\n\n- Name keys and actions only through `src\u002Fhints.rs`: `key::*`, `action::*` and the shared pairs (`hints::NAVIGATE`, `SELECT`, `SEARCH`, `CANCEL`, `CLOSE`, `BACK`). Never write a key or action as a string literal at a call site. A single letter key (`\"d\"`, `\"r\"`) is fine as long as its action comes from `action::*`. When a key or verb is missing, add it to `src\u002Fhints.rs`.\n- A hint is an unpadded `(key, action)` pair (`hints::Hint`). The renderer owns all spacing; never bake spaces into a label.\n- Wording: actions are lowercase verbs (`navigate`, `select`, `close`); keys keep their canonical casing (`Enter`, `Esc`, `Ctrl+C`, `Backspace`). Combined keys use `\u002F` (`Space\u002FEnter`, `Esc\u002FCtrl+C`).\n- Vertical navigation is `key::NAV` (`↑↓\u002Fjk`) whenever j\u002Fk work; use `key::ARROWS` (`↑↓`) only where a focused text field owns the letters. Horizontal navigation is `key::LEFT_RIGHT` (`←→`).\n- Footers read `key action  key action`, ending with the Esc hint. Inline status lines (loading line, narrator) are the one exception and read `key to action`.\n- Render every footer through `ui\u002Fhint_line.rs` (`draw`, `draw_clipped`, `line`, `spans`, `styled`): they apply the shared key\u002Faction styles and clip to the box. Never place hint text with hardcoded x offsets or custom key styles. Center a hint with `hints::width`.\n- Onboarding and dialogs follow the same footer form (`Enter continue`, `Esc back`), not sentences like \"Press Esc to go back\".\n\n## Keyboard navigation\n\n- Every navigable list accepts `j`\u002F`k` alongside `↑`\u002F`↓` when no text field is focused. Match only plain keys (no Ctrl\u002FAlt\u002FSuper) so `Ctrl+J`\u002F`Ctrl+K` keep their editing meaning.\n- Show the navigation keys a screen actually handles: write `↑↓\u002Fjk` only where j\u002Fk are wired.\n- Edges: `↑↓`\u002F`jk` (and `←→` across dialog options) wrap at both ends; PageUp\u002FPageDown\u002FHome\u002FEnd clamp. Move an `OptionList` (`src\u002Foption_list.rs`) with `step(down, len, wrap, selectable)`, whose `selectable` skips rows (section headers, notes, blanks) that cannot take the cursor; `list_nav::wrap` is only for the onboarding's fixed two-choice screens. Never hand-roll `saturating_sub`\u002F`min(len - 1)` for arrow moves. The only lists that do not wrap are the ones attached to the composer: Down past the newest queued prompt leaves queue mode, and Up at the top of the subagent list returns focus to the composer.\n- Back: Esc goes back exactly one level (field → list, detail → list, auth flow → its `\u002Fmcp` list) and closes only at the top level. Backspace edits text and is never a navigation key. A nested view's footer ends with `hints::BACK` (`Esc back`); a top-level view's footer ends with `hints::CLOSE` or `hints::CANCEL`.\n- Digits: a row's digit shortcut exists if and only if the row displays its number (`1. Trust folder`). Pressing it is the same as moving to the row and pressing Enter. Parse it with `list_nav::digit`; never accept digits on unnumbered rows, and never number rows that do not accept their digit.\n\n## Scrolling\n\n- A scrolling list is an `OptionList`: its renderer calls `layout(lines, area)` (the option on each line, `None` for headers) or `layout_rows(len, area)`, which keeps the highlight in view through `ui\u002Flist_scroll.rs` `follow` and records the click hit map; never write its own `scroll = selected` reconciliation. It moves the viewport the least and brings the option's non-selectable neighbours along: its section header above it, the list's leading lines for the first option, the trailing lines for the last one. Wrapping from the bottom back to the top therefore always shows the very top of the list.\n- The wheel and the scrollbar (`wheel`, `detach_at`) free the viewport until the next keyboard move (`step`, `select`); a freed viewport only clamps its offset. `highlight` moves the highlight without reattaching it.\n\n## Mouse\n\n- Every clickable list is an `OptionList\u003CR>`: route its press, drag and release through `mouse::option_gesture` (it keeps text selection working inside the bottom app) or `OptionList::mouse`, and add it to `mouse::option_list` so it gets the wheel, scrollbar and hover. Never hit-test rows by hand.\n- The click rule `R` is part of the list's type and comes from the item's per-item actions, the keys that act on the highlighted item. Navigation, search, Esc and whole-list keys (`r` refresh or reload, Tab switching the save target) do not count.\n  - One action, choosing the item (tool approval, questions, `\u002Ftheme`, `\u002Fplugins`, subagents, config choices, the remote project picker): `SingleAction`, one click confirms. A click yields the option index.\n  - Several actions (`\u002Fmodel` and `\u002Fthinking`: Enter or `s`; `\u002Fresume`: Enter or `d`; `\u002Fmcp`: Enter, `d` or `e`; `\u002Fconfig`: Enter or Ctrl+R): `MultiAction`, a click highlights and a click on the highlight does what Enter does. A click yields `Click::Highlight` or `Click::Confirm`; a highlight click moves like an arrow key (`\u002Fresume` previews).\n- A row's own click targets (the `\u002Flog-level` badges) are one action each, so a click on one acts at once.\n- The free-text row of a question is an input: a click places the caret and a click on its number toggles it in multi-select. It never submits.\n\n## Searchable lists\n\n- Use `search_field::Search`, `search_field::handle_key` and `search_field::paste` for any filterable list, and build its footer with `search_field::hints`.\n- The model: lists open with the list focused; `\u002F` focuses the field; typing filters live (letters, including j\u002Fk, go to the field); `↑↓`, PageUp\u002FPageDown and Enter keep acting on the list while the field is focused; Esc first leaves the field (the filter stays), then clears the filter, then closes the screen.\n- Do not add other entry points into search (Tab, Left, type-to-search on open). Do not make Enter only \"apply\" the filter: it acts on the highlighted item.\n- The list footer includes `hints::SEARCH`.\n- The search row sits directly under the title, followed by one blank row, and reads `\u002F  placeholder` (`Search plugins`, `Search settings`). It is always visible in the list view and hidden in detail views. Draw it only with `ui\u002Fsearch_field.rs` `draw_row`, which owns the `\u002F` and the field's indent; never put a search field at the bottom of a list or in the footer. The project picker is the one exception: its labelled `Search projects:` field shares the form `Field` of its create view.\n\n## Selection\n\n- The focused row is the list-cursor bar: `ui\u002Flist_cursor.rs` `style()` across the full row width (block-cursor colors, bold). No glyph cursors (`›`, `▸`, `>`) for focus.\n- Draw the bar only through `list_cursor`: `paint(f, area)` fills a row area, `styles(highlighted)` \u002F `styles_on(highlighted, bg)` give the `(text, dim)` styles of a row, `marker_style` styles the current-value marker on it. Never read `theme::block_cursor_bg`\u002F`block_cursor_fg` outside `ui\u002Ftheme\u002F` and `ui\u002Flist_cursor.rs` (a unit test enforces it). Text-field carets are not list cursors: use `theme::block_caret` (TextArea-like fields) or `theme::fixed::input_caret` (compact `Input`-like fields).\n- Horizontal options (dialog buttons) render each option as a ` label ` chip; the selected chip takes `list_cursor::style()`. Keep labels at the same columns when switching selection.\n- The current value (the active model, theme, level, layer or session) is marked with `list_cursor::marker(true)` (`› `) in `list_cursor::current_color()`, in a two-column slot that stays blank (`list_cursor::BLANK`) on other rows.\n- `(String, Style)` row renderers paint the full-width bar for rows where `list_cursor::is_bar` holds, and keep a span's own background instead of overwriting it.\n\n## Colors\n\n- Every color value lives in `src\u002Fui\u002Ftheme\u002F`: theme-dependent colors in the theme palettes (`theme::foreground()`, `theme::muted_style()`, ...), fixed brand and terminal colors in `ui\u002Ftheme\u002Ffixed.rs` (`ORANGE`, `LOADING_GRADIENT`, onboarding colors, `sgr::*` escape codes, the Monokai\u002FAlabaster named palette via `fixed::named`), syntax colors in `ui\u002Ftheme\u002Fsyntax.rs`. A fixed color such as the brand orange is fine, but it is defined once there and imported everywhere else.\n- Outside `src\u002Fui\u002Ftheme\u002F`, never write `Color::Rgb(..)`, `Color::Indexed(..)`, a named `Color::*` variant or a raw SGR color code. When a screen needs a new color, add a named constant or theme accessor first. `tests\u002Funits\u002Fcolor_literals.rs` fails on any literal outside the theme module (only `update_prompt\u002Fansi.rs`, which converts any `Color` to SGR, and test code are exempt).\n\n## Verification\n\n- Any change to a hint, a key, a list behavior (wrap, back, digits, scroll, search, clicks) or a selection style is user-visible: update the affected `client-e2e` scenarios (`screen_contains`, key sequences, mouse coordinates) and regenerate their goldens as described in `vibe\u002Fcli-rust\u002FAGENTS.md`. A new behavior gets its own scenario (for example `mcp\u002Fmcp_wrap_scroll`).\n- Shared helpers carry their own unit tests (`tests\u002Funits\u002Foption_list.rs`, `option_clicks.rs`, `list_nav.rs`, `list_scroll.rs`, `search_field.rs`); extend them when a helper changes instead of testing the rule screen by screen.\n- `tests\u002Funits\u002Fcolor_literals.rs` guards the color and list-cursor rules. Do not add exemptions to make it pass: move the color into `src\u002Fui\u002Ftheme\u002F` or route the bar through `list_cursor`.\n","# Vibe Rust TUI\n\nUI conventions for `vibe\u002Fcli-rust\u002F`. Every screen follows them so the TUI reads as one product. Local code rules, scenarios and goldens live in `vibe\u002Fcli-rust\u002FAGENTS.md` and `client-e2e\u002FAGENTS.md`.\n\n## Shortcut hints\n\n- Name keys and actions only through `src\u002Fhints.rs`: `key::*`, `action::*` and the shared pairs (`hints::NAVIGATE`, `SELECT`, `SEARCH`, `CANCEL`, `CLOSE`, `BACK`). Never write a key or action as a string literal at a call site. A single letter key (`\"d\"`, `\"r\"`) is fine as long as its action comes from `action::*`. When a key or verb is missing, add it to `src\u002Fhints.rs`.\n- A hint is an unpadded `(key, action)` pair (`hints::Hint`). The renderer owns all spacing; never bake spaces into a label.\n- Wording: actions are lowercase verbs (`navigate`, `select`, `close`); keys keep their canonical casing (`Enter`, `Esc`, `Ctrl+C`, `Backspace`). Combined keys use `\u002F` (`Space\u002FEnter`, `Esc\u002FCtrl+C`).\n- Vertical navigation is `key::NAV` (`↑↓\u002Fjk`) whenever j\u002Fk work; use `key::ARROWS` (`↑↓`) only where a focused text field owns the letters. Horizontal navigation is `key::LEFT_RIGHT` (`←→`).\n- Footers read `key action  key action`, ending with the Esc hint. Inline status lines (loading line, narrator) are the one exception and read `key to action`.\n- Render every footer through `ui\u002Fhint_line.rs` (`draw`, `draw_clipped`, `line`, `spans`, `styled`): they apply the shared key\u002Faction styles and clip to the box. Never place hint text with hardcoded x offsets or custom key styles. Center a hint with `hints::width`.\n- Onboarding and dialogs follow the same footer form (`Enter continue`, `Esc back`), not sentences like \"Press Esc to go back\".\n\n## Keyboard navigation\n\n- Every navigable list accepts `j`\u002F`k` alongside `↑`\u002F`↓` when no text field is focused. Match only plain keys (no Ctrl\u002FAlt\u002FSuper) so `Ctrl+J`\u002F`Ctrl+K` keep their editing meaning.\n- Show the navigation keys a screen actually handles: write `↑↓\u002Fjk` only where j\u002Fk are wired.\n- Edges: `↑↓`\u002F`jk` (and `←→` across dialog options) wrap at both ends; PageUp\u002FPageDown\u002FHome\u002FEnd clamp. Move an `OptionList` (`src\u002Foption_list.rs`) with `step(down, len, wrap, selectable)`, whose `selectable` skips rows (section headers, notes, blanks) that cannot take the cursor; `list_nav::wrap` is only for the onboarding's fixed two-choice screens. Never hand-roll `saturating_sub`\u002F`min(len - 1)` for arrow moves. The only lists that do not wrap are the ones attached to the composer: Down past the newest queued prompt leaves queue mode, and Up at the top of the subagent list returns focus to the composer.\n- Back: Esc goes back exactly one level (field → list, detail → list, auth flow → its `\u002Fmcp` list) and closes only at the top level. Backspace edits text and is never a navigation key. A nested view's footer ends with `hints::BACK` (`Esc back`); a top-level view's footer ends with `hints::CLOSE` or `hints::CANCEL`.\n- Digits: a row's digit shortcut exists if and only if the row displays its number (`1. Trust folder`). Pressing it is the same as moving to the row and pressing Enter. Parse it with `list_nav::digit`; never accept digits on unnumbered rows, and never number rows that do not accept their digit.\n\n## Scrolling\n\n- A scrolling list is an `OptionList`: its renderer calls `layout(lines, area)` (the option on each line, `None` for headers) or `layout_rows(len, area)`, which keeps the highlight in view through `ui\u002Flist_scroll.rs` `follow` and records the click hit map; never write its own `scroll = selected` reconciliation. It moves the viewport the least and brings the option's non-selectable neighbours along: its section header above it, the list's leading lines for the first option, the trailing lines for the last one. Wrapping from the bottom back to the top therefore always shows the very top of the list.\n- The wheel and the scrollbar (`wheel`, `detach_at`) free the viewport until the next keyboard move (`step`, `select`); a freed viewport only clamps its offset. `highlight` moves the highlight without reattaching it.\n\n## Mouse\n\n- Every clickable list is an `OptionList\u003CR>`: route its press, drag and release through `mouse::option_gesture` (it keeps text selection working inside the bottom app) or `OptionList::mouse`, and add it to `mouse::option_list` so it gets the wheel, scrollbar and hover. Never hit-test rows by hand.\n- The click rule `R` is part of the list's type and comes from the item's per-item actions, the keys that act on the highlighted item. Navigation, search, Esc and whole-list keys (`r` refresh or reload, Tab switching the save target) do not count.\n  - One action, choosing the item (tool approval, questions, `\u002Ftheme`, `\u002Fplugins`, subagents, config choices, the remote project picker): `SingleAction`, one click confirms. A click yields the option index.\n  - Several actions (`\u002Fmodel` and `\u002Fthinking`: Enter or `s`; `\u002Fresume`: Enter or `d`; `\u002Fmcp`: Enter, `d` or `e`; `\u002Fconfig`: Enter or Ctrl+R): `MultiAction`, a click highlights and a click on the highlight does what Enter does. A click yields `Click::Highlight` or `Click::Confirm`; a highlight click moves like an arrow key (`\u002Fresume` previews).\n- A row's own click targets (the `\u002Flog-level` badges) are one action each, so a click on one acts at once.\n- The free-text row of a question is an input: a click places the caret and a click on its number toggles it in multi-select. It never submits.\n\n## Searchable lists\n\n- Use `search_field::Search`, `search_field::handle_key` and `search_field::paste` for any filterable list, and build its footer with `search_field::hints`.\n- The model: lists open with the list focused; `\u002F` focuses the field; typing filters live (letters, including j\u002Fk, go to the field); `↑↓`, PageUp\u002FPageDown and Enter keep acting on the list while the field is focused; Esc first leaves the field (the filter stays), then clears the filter, then closes the screen.\n- Do not add other entry points into search (Tab, Left, type-to-search on open). Do not make Enter only \"apply\" the filter: it acts on the highlighted item.\n- The list footer includes `hints::SEARCH`.\n- The search row sits directly under the title, followed by one blank row, and reads `\u002F  placeholder` (`Search plugins`, `Search settings`). It is always visible in the list view and hidden in detail views. Draw it only with `ui\u002Fsearch_field.rs` `draw_row`, which owns the `\u002F` and the field's indent; never put a search field at the bottom of a list or in the footer. The project picker is the one exception: its labelled `Search projects:` field shares the form `Field` of its create view.\n\n## Selection\n\n- The focused row is the list-cursor bar: `ui\u002Flist_cursor.rs` `style()` across the full row width (block-cursor colors, bold). No glyph cursors (`›`, `▸`, `>`) for focus.\n- Draw the bar only through `list_cursor`: `paint(f, area)` fills a row area, `styles(highlighted)` \u002F `styles_on(highlighted, bg)` give the `(text, dim)` styles of a row, `marker_style` styles the current-value marker on it. Never read `theme::block_cursor_bg`\u002F`block_cursor_fg` outside `ui\u002Ftheme\u002F` and `ui\u002Flist_cursor.rs` (a unit test enforces it). Text-field carets are not list cursors: use `theme::block_caret` (TextArea-like fields) or `theme::fixed::input_caret` (compact `Input`-like fields).\n- Horizontal options (dialog buttons) render each option as a ` label ` chip; the selected chip takes `list_cursor::style()`. Keep labels at the same columns when switching selection.\n- The current value (the active model, theme, level, layer or session) is marked with `list_cursor::marker(true)` (`› `) in `list_cursor::current_color()`, in a two-column slot that stays blank (`list_cursor::BLANK`) on other rows.\n- `(String, Style)` row renderers paint the full-width bar for rows where `list_cursor::is_bar` holds, and keep a span's own background instead of overwriting it.\n\n## Colors\n\n- Every color value lives in `src\u002Fui\u002Ftheme\u002F`: theme-dependent colors in the theme palettes (`theme::foreground()`, `theme::muted_style()`, ...), fixed brand and terminal colors in `ui\u002Ftheme\u002Ffixed.rs` (`ORANGE`, `LOADING_GRADIENT`, onboarding colors, `sgr::*` escape codes, the Monokai\u002FAlabaster named palette via `fixed::named`), syntax colors in `ui\u002Ftheme\u002Fsyntax.rs`. A fixed color such as the brand orange is fine, but it is defined once there and imported everywhere else.\n- Outside `src\u002Fui\u002Ftheme\u002F`, never write `Color::Rgb(..)`, `Color::Indexed(..)`, a named `Color::*` variant or a raw SGR color code. When a screen needs a new color, add a named constant or theme accessor first. `tests\u002Funits\u002Fcolor_literals.rs` fails on any literal outside the theme module (only `update_prompt\u002Fansi.rs`, which converts any `Color` to SGR, and test code are exempt).\n\n## Verification\n\n- Any change to a hint, a key, a list behavior (wrap, back, digits, scroll, search, clicks) or a selection style is user-visible: update the affected `client-e2e` scenarios (`screen_contains`, key sequences, mouse coordinates) and regenerate their goldens as described in `vibe\u002Fcli-rust\u002FAGENTS.md`. A new behavior gets its own scenario (for example `mcp\u002Fmcp_wrap_scroll`).\n- Shared helpers carry their own unit tests (`tests\u002Funits\u002Foption_list.rs`, `option_clicks.rs`, `list_nav.rs`, `list_scroll.rs`, `search_field.rs`); extend them when a helper changes instead of testing the rule screen by screen.\n- `tests\u002Funits\u002Fcolor_literals.rs` guards the color and list-cursor rules. Do not add exemptions to make it pass: move the color into `src\u002Fui\u002Ftheme\u002F` or route the bar through `list_cursor`.\n",{"name":5,"metadata":48,"description":7},{"display-name":49,"default-prompt":50,"short-description":51},"Vibe Rust TUI","Use $vibe-rust-tui to follow the Rust TUI hint, keyboard, navigation, search, list-cursor and color conventions.","Hint, keyboard, navigation, mouse, search, list-cursor and color conventions for the Rust TUI","main","338ad4bf0f73c4dd879d667cf7ab011555ae1751",".agents\u002Fskills\u002Fvibe-rust-tui",796,"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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add mistralai\u002Fmistral-vibe --skill vibe-rust-tui",{"tool":66,"command":67},"bunx","bunx skills add mistralai\u002Fmistral-vibe --skill vibe-rust-tui",{"tool":69,"command":70},"pnpm","pnpm dlx skills add mistralai\u002Fmistral-vibe --skill vibe-rust-tui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvibe-rust-tui\u002FSKILL.md",true,[],[75,104,125,149,169,189],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":43},"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",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,87,88,89,90,91,92,93,94,95,24,96,97,98,23,99,100,101,102,103],"setup","file","configuration","mcp servers","servers","plugins","commands","instructions","opencode","codex","permissions","code","load","MCP","reuse","hooks","switch",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":43},"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",[],[106,111,112,26,113,114,115,116,117,34,118,37,119,120,121,122,123,23,124,101],"clean","worktrees","home","up","user","git worktrees","remove","git worktree","work","create","git","true","task","Existing",{"skillNo":126,"name":22,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":43},"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",[130],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[22,132,133,26,134,135,136,137,138,139,140,141,142,143,144,145,146,100,147,148],"themes","you","do","act","log","Meta","inspect","project","subagents","config","why","how","command","change","logs","question","local",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":43},"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",[155],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[157,158,159,160,161,22,162,163,133,164,99,165,166,167,168],"creator","skill creator","plan","flow","support","add","it","frontmatter","files","permission","directory","discovery",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":43},"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",[175],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[120,177,178,115,91,179,180,181,23,182,26,183,184,12,34,185,100,90,186,92,102,187,188],"plugin","create plugin","with","extensions","author","agent plugins","connectors","scaffold","package","knowledge","format","libraries",{"skillNo":190,"name":191,"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":192,"categories":193,"keywords":194,"publishedAt":43},"01M6C4620AT7K4999KR0YY86KH","prompts","https:\u002F\u002Fgithub.com\u002Fmistralai\u002Fmistral-vibe\u002Fblob\u002Fmain\u002Fvibe\u002Fcore\u002Ftools\u002Fbuiltins\u002Fprompts\u002Fskill.md",[],[191]]