Prompts and Skills
Prompts and skills are instructions you store once in Studio and reuse everywhere, instead of copying them into each application.
- A prompt is a text template, such as a system prompt, with optional
{{variable}}placeholders. Applications fetch it by name and pass its content to a model. - A skill packages a method: a description of when to use it, instructions, and optional files, such as templates, reference material, or scripts. Skills follow the open Agent Skills format, and an assistant loads a skill only when a task matches its description.
Both are versioned and shareable, so domain experts can improve a prompt or a skill, and every application that uses it picks up the change without a code release.
Versions and aliases
Every change to the content of a prompt or a skill creates a new, numbered version. Earlier versions stay available for review and rollback.
An alias, such as staging or production, is a name that points to one version. Your code asks for the alias, and you decide in Studio or through the API which version it points to. To promote a tested version, point the alias at it.
For more information, see Versions and aliases.
A new prompt or skill is private: only you can see it. To let teammates find and use it, share it with your workspace. When you share it, choose whether workspace members can only read it or also edit it.
Where you use them
| Prompts | Skills | |
|---|---|---|
| Studio | Create, version, and share | Create, version, and share |
| API and SDKs (beta) | Fetch by version or alias, then pass the content to a chat completion | Create, version, and fetch with their files |
| Vibe | Not available | Publish a skill to Vibe, then use it in Vibe Work |
| Mistral MCP | List prompts, read a version by number or alias, and write a new version from an MCP client | Browse and read skills and their files, write a new version, change sharing, or delete a skill from an MCP client |