Create your first Skill

Package a repeatable method into a Skill so Vibe›Work ↗ applies the same procedure, format, and tone every time the task matches.

Skills follow the open Agent Skills standard. Each Skill is a folder with a SKILL.md file (instructions + metadata) and optional files (templates, references, examples). Work loads only the relevant Skills into context via progressive disclosure, so you can have many enabled without bloat.

Time to complete: ~10 minutes

• A Mistral account with Vibe Work access. Workspace admins can force-enable or disable Skills at the workspace level.
• A repeatable task you handle often. Good first candidates: a meeting summary template, a code-review checklist, a weekly-report format.

Before building your own, see what a Skill does in practice. Vibe Work ships with built-in Skills you can invoke immediately. Try /deep-research:

/deep-research What are the main approaches to long-context LLMs in 2026?

Work plans the search, runs multiple web queries, synthesizes the sources, and returns a structured brief with citations in Canvas. That's a Skill in action: one trigger, a packaged procedure, a consistent output format.

Now create your own to capture a procedure you reuse.

1. Open Vibe›chat.mistral.ai ↗ and switch to the Work tab.
2. In the left sidebar, open Context > Skills.
3. Click New Skill.

You'll see three sections: Built-in (shipped with Vibe Work), Personal (only you see them), and Workspace (shared with your team).

The form has three fields. The description is the most important: it tells Work when to activate the Skill.

Write the description as a trigger condition:

• Vague: "Helps with meetings."
• Specific: "Use when reviewing customer-call transcripts to extract objections and next steps."

The specific version is what makes Work pick the Skill up reliably at discovery.

In the SKILL.md field, write the procedure Work should follow. Be explicit about format, tone, and what to avoid:

When given meeting notes or a transcript, produce:

1. A one-paragraph executive summary (max 80 words).
2. A bulleted list of action items with owners and due dates if available.
3. A list of open questions.

Tone: professional, concise. Don't invent information that isn't in the source. If owners or dates are missing, mark them as [TBD].

Keep instructions tight. If a step needs an example, attach a sample file or template alongside the Skill (templates, references, brand guidelines, sample outputs). Work loads them as needed when the Skill activates.

1. Click Create Skill to register it.
2. Start a new Work task and paste a real example of the source material (meeting notes, transcript, etc.).
3. Watch the todos panel: if the description matches, Work picks the Skill up automatically. You can also invoke it explicitly with /{skill-name} or by mentioning it in your prompt.
4. Compare the output to your expected format. Iterate on the SKILL.md if anything is off.

If the Skill is useful beyond your own work, Publish it to the workspace:

1. From the Skills view, open the Skill.
2. Click Publish to make it available to teammates in the same workspace.
3. Workspace admins can also force-enable specific Skills for everyone in the workspace.

Your Skill is working if:

• It appears in the Skills view under the correct scope (Personal or Workspace).
• Work activates it automatically on matching tasks (you'll see it referenced in the todos).
• The output follows your format, tone, and constraints consistently across different inputs.