- Get Started

Adding a Skill

Skills are how you teach a role something new — a specific workflow, a project convention, a linting process — without writing any system code. This is one of the most common extensions, and it's configuration-only.

What a skill is

A skill is a packaged set of instructions a role can load on demand. It typically captures a repeatable capability: "how this project runs its checks," "the conventions we follow for this kind of work," "the steps for that process."

Skills are scoped per role, so you can give the builder a coding skill and the reviewer a review skill without the two looking alike.

Before you start

Steps

  1. Create the skill. Put the skill definition — its name and instructions — in the skills area of the orchestration content. A skill is essentially a folder with an instruction file inside.
  2. Assign it to a role in the registry. Open the agent registry for the role and add the skill to that role's skill list.
  3. Apply it. Save the registry change through the control panel. It's validated and takes effect on the team's next cycle — no restart and no redeploy.

What you should see

Notes

Going further

Model and tool side-by-side

Skills, MCP servers, and models are the three per-role capability extensions, and all are configuration-only. They compose: a role can carry several skills, reach several servers, and run on whatever model suits its job. See Agent Setup for how they fit together in the registry.