Skip to main content
A skill teaches your assistant a procedure: an ordered composition of workflows it runs conditionally on your behalf. Where a workflow is a single automation, a skill strings automations together with the conditions for when each applies — authored by your team, executed by the assistant.

​
How skills work

  • Authoring. Write a skill as ordered steps that reference your existing workflows, with conditions controlling which steps run. Kelasa validates the skill as you author it — including that every referenced workflow exists and is runnable.
  • Versions. Like workflows, skills are versioned: edits create a new version you publish deliberately.
  • Execution. When you ask the assistant for something a skill covers, it runs the skill’s steps in order, evaluating conditions as it goes. Each underlying workflow run appears in history like any other run.
  • Approvals. Skills inherit the same guardrails as everything else: side-effecting steps pause for confirmation, and skill runs can require approval before they start.

​
When to use a skill vs. a workflow

​
Example

“Onboard a new engineer” as a skill: create accounts (workflow), grant repo access (workflow), schedule intro meetings (workflow) — with a condition that the access-granting step only runs for engineering hires. Ask the assistant to onboard someone, confirm the side effects, and it works through the steps.