Skills
Reusable workflows and standard operating procedures — deployment steps, review checklists as prose, and more.
Skills document reusable workflows: standard operating procedures, development processes, code review procedures, deployment workflows, and step-by-step task execution guides.
What a Skill is for
Structurally, a Skill is identical to a Context or Instruction — title, description, Markdown content, draft/published status, and version history. Think of it as the resource type for "how we do this task, step by step," as opposed to a fact about the system (Context) or a rule to obey (Instruction).
Good candidates for a Skill: "How We Cut a Release," "How We Triage an Incoming Bug," "How to Onboard a New Service to the Deploy Pipeline," "How to Roll Back a Bad Deploy."
Creating a Skill
- Open a project and go to its Skills tab.
- Click Create, add a title and description, and write the procedure as ordered steps in the Markdown editor — numbered lists map naturally onto a sequence of actions.
- Save. It starts as v1, in draft, exactly like every other content-bearing resource.
A good Skill reads like a runbook: concrete steps, in order, with any decision points called out explicitly ("if X, do Y instead").
Editing, versions, and publishing
Same model as every content-bearing resource type: title/description edits are separate from content edits, content edits create a new version rather than replacing what's live, and an org admin promotes a version to Main to publish it. Full details in Versioning & Publishing.
Who can write
Creating, editing, publishing, and deleting a Skill requires org-admin-level project access (owner/moderator). Everyone with project access can read every Skill, draft or published.
Bundling into an Agent Profile
A Skill is one of the five resource types you can pull into an Agent Profile — e.g. bundling your "How We Cut a Release" Skill into a "Release Manager" profile alongside relevant Checklists and Instructions.