Writing & chat · guidance updated 15 Nov 2026

Mistral (Le Chat / Vibe) prompt guide

Work unifies chat and agentic workflows. Use fast/think toggle for conversational or reasoning depth. Always review outputs as drafts—verify facts, dates, names, and source references before use.

Free. We don't store what you type.

How to prompt Mistral (Le Chat / Vibe)

  1. Start with 'You are a [role]; your task is to [task].'
  2. Describe the outcome, not steps—Work breaks down and routes automatically.
  3. Name sources explicitly: Files, Connectors (Gmail, Outlook, Slack, Notion, Linear, GitHub, Stripe, Atlassian, Google Drive, SharePoint), Libraries, Skills (@), or web search.
  4. State audience, length, tone, format, and deadline as constraints.
  5. Use objective measures ('200 words', '3 bullets') instead of 'short', 'interesting', 'better'.
  6. Organize longer prompts into Markdown or XML sections for readability.
  7. Avoid contradictions; use decision trees (if/then chains) when logic branches.
  8. Avoid subjective words ('too long', 'many', 'stuff') and blurry adjectives.
  9. Provide few-shot examples (input/output pairs) to clarify format and behavior.
  10. Use fast/think toggle: fast for turn-based chat, think for planning and complex reasoning.
  11. Reference Skills with @ for repeatable templates and methods.
  12. Treat Work outputs as drafts; verify facts, dates, names, and references before using or sharing.
  13. Expect approval prompts before sensitive actions; stay in control by monitoring progress and todos.

The shape of a good prompt

You are a [role]; your task is to [task].
## Context
[files, Connectors, Libraries, Skills (@), or web search]
## Audience
[who reads this]
## Constraints
[length, tone, format, deadline, decision rules as if/then]
## Examples
[input/output pairs if format clarity needed]
## Output
[format, sections, word-based scales]

Avoid

  • Subjective size or quality words ('too long', 'interesting', 'better')
  • Contradictory instructions without clear priority or decision tree
  • Numeric rating scales; use word-based scales instead
  • Micromanaging Work's steps; let it plan and ask approval for sensitive actions
  • Blurry quantifiers ('many', 'few', 'stuff', 'things')
  • Treating Work output as final before review; always verify facts, dates, and references
  • Assuming Work outputs are production-ready without human review

Example

Request make a one page brief on electric bikes for my team

You are a market analyst; your task is to produce a one-page brief on the European e-bike market.

## Context
Research the web for sources from the last 18 months. My team is deciding whether to stock e-bikes in our UK bike shops.

## Audience
Shop managers with no analyst background.

## Constraints
- Under 400 words
- Plain, neutral tone
- If data is UK-specific, prefer it; otherwise use EU data and say so

## Output
Sections: Market size and growth, Top-selling categories, Price bands, Risks, Recommendation. Rate overall opportunity as Low, Medium or High and cite sources for each figure.

The Weekly Tally

Useful updates, insights and no-hype advice. Read this week's digest.

One email a week. Unsubscribe in one click.