Skills
Reusable, no-code instruction sets the assistant follows on demand.
Skills
A skill is a saved set of instructions the assistant follows when you invoke it — a repeatable workflow captured once and reused by anyone it is shared with. No code involved: a skill is written in plain language.
Examples: "Summarise a batch record in our QA format", "Draft a customer quotation from the price list", "Answer safety questions citing only the current SOP revision".
Manage skills from Skills in the sidebar.
What a skill contains
| Field | Purpose |
|---|---|
| Name | How the skill appears in the / menu |
| Description | One line shown in pickers |
| When to use | Hint that helps the assistant apply the skill at the right time |
| Instructions | The actual steps the assistant follows — the core of the skill |
| Output format | Optional — the structure the answer or document should take |
| Linked template | Optional — an org DOCX template to fill when the skill generates a document |
Personal and organisation skills
- Personal skills — any user can create them. Visible only to you.
- Organisation skills — created by org admins, or by group admins for their own groups. Visibility is group-scoped: members see an org skill only if it is assigned to a group they belong to.
- Promoting — the owner of a personal skill can promote it to an organisation skill, provided they are an admin (or group admin of every target group).
Each skill has an enabled toggle. Only enabled skills appear in chat.
Using a skill in chat
Type / in the chat input. A menu of your available skills (and document templates) opens — keep typing to filter by name, then press Enter or click to select. The chosen skill appears as a token in the input; press Backspace to remove it.
The assistant can also apply a skill on its own: enabled skills' names and "when to use" hints are visible to it, and when your request clearly matches one, it loads that skill's instructions for the turn. Selecting a skill explicitly with / is the reliable way to guarantee it is used.
Writing good skills
- Be concrete in the instructions — name the documents, sections, and terminology the assistant should use
- Fill in "when to use" — it is what lets the assistant pick the skill up automatically
- Specify the output format if the result must follow a fixed structure (report sections, table columns)
- Link a template when the skill should produce a formatted Word document — see Document Generation