Mistral Vibe: /skills Manager Gets Edit, Delete, Create and Share Actions
The Mistral Vibe /skills manager now lists skills that failed to load with the reason, shows each skill's file, and lets users edit (e), delete (x), create (n) and share skills. It also opens while the agent works.
Key Takeaways
/skillsnow lists skills that failed to load, with file and reason.- Press
eto edit,xto delete with a confirmation naming the folder, andnto create a skill. - In the Shared tab,
aadds andrremoves a shared skill. - The manager opens during a turn, and changes apply when the turn ends.
- Skill pages render
SKILL.mdas markdown after the description and metadata. - A malformed
skills.tomlis reported rather than erased when pins change.
More actions from one screen
Mistral Vibe 3.1.4 extends the /skills manager. It lists skills that failed to load along with their file and the reason, and shows each skill's file. Pressing e opens a local skill in the user's editor, and a skill edited this way shows its new content once the editor closes. Pressing x deletes a skill after a confirmation that names its folder, and n starts a new skill with the skill creator. In the Shared tab, a adds the highlighted skill and r removes a shared skill at once.
Layout and behavior
/skills now opens while the agent works, and a change made during a turn applies when the turn ends. The list shows the highlighted skill's description above its rows instead of its body, and the tabs show their counts and switch with Tab, Shift+Tab and the left and right arrows. A skill's page opens on its description, then status, source, scope and file, then its SKILL.md rendered as markdown. My Skills is sorted by name and the box keeps the height it opened with.
Related fixes
A skill whose metadata or allowed-tools frontmatter has the wrong type is now reported instead of breaking plugin loading. Adding or removing a shared skill no longer erases the other pins of a skills.toml that cannot be parsed. The /plugins page also now leads with the description, then facts under dim labels, then components by kind, and long paths wrap.