Skip to main content

✨What are skills?

Teach the agent your workflow once, so the team never has to explain it again.

Written by Even Dalen

A skill is a workflow you give the agent: a name, a short description of when to use it, and the instructions the agent should follow. The agent can put a skill to use on its own when the task fits, or you can ask it to use a specific skill.

Skills are shared with everyone in the workspace. Once one person has worked out a good way to quality-check a bid, the whole team can follow the same approach.

You'll find skills under "Library" in the menu, right after "AI instructions".

Skills or AI instructions?

The two are easy to mix up, but they do different jobs:

  • AI instructions are always active. They cover tone, preferences, and fixed rules that apply no matter what the agent is working on.

  • A skill is pulled in when the task fits. It's an approach for one kind of work, such as "review the compliance matrix" or "select reference projects".

Think of AI instructions as the house rules, and skills as the recipes.

Create a skill

  1. Go to "Library" → "Skills".

  2. Click "Create skill".

  3. Give the skill a name. Use plain language — the name has to be unique, but it doesn't have to be technical.

  4. Write a short description of when the agent should use the skill. This one matters: the description is what the agent reads when deciding whether the skill fits the task.

  5. Write the instructions the agent should follow. Be concrete, and put the steps in order.

  6. Click "Create". The skill is active from the start.

A workspace can have up to 50 active skills at a time. Deactivate a skill to free up space without deleting its content.

The description is what lets the agent find the skill on its own. "Check the compliance matrix before submission" works better than "Miscellaneous quality assurance".

How the agent uses the skill

The agent sees the name and description of every active skill, and pulls in the instructions when a task fits. You can also ask for one directly — "use the compliance matrix skill" is enough, you don't need to type a technical name.

The agent can read skills but not change them. Only workspace administrators create and edit skills.

Edit, deactivate, or delete

Click the three dots on the skill's row:

  • Edit — adjust the name, description, or instructions. The change applies to the whole team immediately.

  • Deactivate — the skill stays, but the agent stops using it. Useful when an approach is outdated and you don't want to lose the content.

  • Delete — removes the skill for the whole workspace.

The list shows active skills by default. Choose "All" to see deactivated ones too — they're marked "Inactive".

Tips

  1. Start with one skill for the workflow you repeat most often.

  2. Write the instructions like a recipe, with steps in order, rather than as one long paragraph.

  3. Say what the agent should do when something is unclear — for example "flag claims that need verification" instead of letting it guess.

  4. Keep skills small and specific. One skill per workflow works better than one big skill meant to cover everything.

  5. If an approach is still being trialled, deactivate it rather than deleting it.

Did this answer your question?