Stevin Manual/Features/Skills Draft preview Updated November 19, 2026

Skills

Skills are instructions you write for Stevin so it does recurring work the way your team does. How skills work and how to write a good one.

What a skill is#

A skill is a set of instructions that tells Stevin how to do a kind of job: when it applies, the steps, what to watch for, and what the deliverable looks like. When Stevin recognizes a matching task, it reads the skill before it starts.

Think of it as the operating manual you would give a new colleague. Write it once and it is followed every time, with no repeated explaining.

When to write a skill#

  • You have explained the same kind of task to Stevin three times or more.
  • Your team has a fixed format or rule for it, such as a weekly report template or a ticket severity standard.
  • Mistakes are costly and it must follow the steps strictly, as with refunds.

Team skills and your own skills#

Type Who writes it Who it applies to
Your own skill Any member Only you: only your conversations use it
Team skill Admins Everyone in the workspace

Once a skill of your own has proved useful, an admin can publish it to the team. Creating, switching on and publishing skills is done in the console; see Manage skills.

The parts of a skill#

Part What to write
Name Short, lowercase, with hyphens, such as weekly-report
What it does One or two sentences on the situations it applies to. Stevin uses this to decide when to use the skill, so be specific
Full instructions What Stevin reads when it uses the skill
Extra material Optional files with finer detail (templates, examples), which Stevin opens only when it needs them

A template you can edit#

## When to use
When someone asks for a weekly report or mentions "this week's summary".

## Steps
1. Confirm the time range; the default is this Monday to today.
2. Read merged pull requests from GitHub and completed issues from Linear.
3. Organize them into three parts: Done / In progress / Risks.
4. Post to the place the person named; if none, reply in the current conversation.

## Notes
- One line per item at most, with a link.
- Write "None" for an empty part; do not leave it out.

What makes a good skill#

  • The description decides whether it gets used. Spell out the triggering situation rather than a vague "handles weekly reports".
  • Steps must be executable. Write "read field Y of table X", not "understand the situation".
  • State the limits. Say when to stop and ask a person, and what not to do.
  • One skill, one job. Split one that grows too long.

Skills and permissions#

A skill is only instructions. It gives Stevin no extra access. The tools a skill uses still have to be connected and reviewed, and the write actions in it still go through approval.

Last updated November 19, 2026 Suggest an edit