Skills

Skills are reusable blocks of instructions and knowledge that you write once and let Agent steps draw on at run time. Instead of repeating the same guidance in every prompt — how to read a particular vendor's invoices, your house style for replies, a checklist a reviewer must follow — you capture it in a Skill and reference it across many Actions.

Skills use the SKILL.md format: a short YAML frontmatter block (name and description) followed by Markdown instructions.

Where to Find Skills

Open Skills from the Agents group in the left navigation. The page has two parts:

• AI Skills list on the left — search and select existing skills.
• The skill editor on the right — create or edit the selected skill.

Any tenant member with edit permission can create, edit, and delete Skills. Read-only members can view them.

How a Skill Is Used

A Skill is loaded by its Context Key — a short identifier that an Agent step looks up when it runs. The context key can be fixed (for example reply-style) or built from run data using variable substitution, such as vendor-{{inputs.vendorId}}. When the step runs, Studio resolves the key, finds the matching enabled Skill, and makes its content available to the model.

This means you can keep one Skill per vendor, per document type, or per policy, and have the right one selected automatically based on the data flowing through the Action.

Creating a Skill

1. Go to Skills and select New.
2. Fill in the fields:
   • Name — a clear, human-readable title, for example Vendor Guideline.
   • Context Key — the identifier Agent steps use to load the Skill. Supports {{inputs.fieldName}} substitution.
   • Description — a one-line summary of what the Skill does.
   • Tags — optional, comma-separated labels for organizing and searching.
   • Skill Enabled — leave on to make the Skill available; turn off to retire it without deleting. Disabled Skills are not loaded into Actions.
   • Content — the instructions, in SKILL.md format (YAML frontmatter between --- markers, then Markdown).
3. Select Save.

Use the search box at the top of the list to filter by name, context key, description, or tags.

Moving Skills Between Tenants

Skills can be exported and imported as JSON, which is useful when promoting work from a UAT tenant to Production:

• Export — select a Skill, then select Export to copy its JSON.
• Import — select Import, paste the JSON, and confirm.

When an Action that bundles default Skills is imported, those Skills are created automatically in the target tenant. A Skill whose context key already exists is kept as-is and is never overwritten. See Promoting from UAT to Production.

Good Practice

• Keep each Skill focused on one topic, so it can be reused and updated independently.
• Name the context key for what the Skill is, and use substitution only when you genuinely need a different Skill per record.
• Disable rather than delete a Skill you might need again — that keeps its history and avoids breaking Actions that reference it.
• Write the content as if briefing a new colleague: concrete rules, examples, and the decisions you want made consistently.

Related Pages

• Agent Steps — the step type that uses Skills.
• Inputs and Tools — other resources Agent steps draw on.

---