Skip to main content
A skill is a named bundle of instructions (and optional reference files) that extends an agent for a specific task. Skills let you teach an agent how to handle a well-defined job without rewriting its core instructions every time. A support agent might have a “warranty lookup” skill, an RFP agent might have a “crossover” skill, a sales agent might have a “quote drafting” skill. The agent picks up a skill when the question matches what the skill was built for, following the skill’s instructions and consulting any files you attached to it.

​
When to add a skill

Create a skill when you find yourself:
  • Pasting the same multi-step instructions into chats with the same agent.
  • Telling the agent to follow a specific procedure that isn’t obvious from the documents in its indexes.
  • Giving the agent a small reference (a lookup table, an internal glossary, a calibration procedure) that doesn’t warrant its own index.
If the behavior you want applies to every question the agent handles, put it in the agent’s core instructions instead. Skills are for task-specific behavior the agent should apply only when relevant.

​
The Skills tab

Open the agent in the admin console and select the Skills tab. The tab shows a card titled Agent Skills with the description “Skills define specialized capabilities for the agent. Each skill has a name, instructions, and optional files.” If no skills are configured yet, the card shows “No skills configured for this agent.” Existing skills appear as collapsible rows, each with the skill name on the header and a trash icon to delete it. Click a row to expand it and edit the instructions or files.

​
Adding a skill

1

Click Add Skill

The + Add Skill button at the top of the Skills card opens an inline form for a new skill.
2

Name the skill

Enter a short, descriptive Name in the text field. Names are how you and your team recognize the skill in the list, so pick something specific: warranty-lookup, crossover, rfp-intake. You can’t rename a skill after saving, so take a moment to pick a good one.
3

Write the instructions

In the Instructions markdown editor, describe what the skill does and how the agent should approach the task. Write it in the second person, directed at the agent:
# Warranty Lookup

When the user asks whether a unit is under warranty:

1. Ask for the serial number if they haven't provided it.
2. Look up the unit in the warranty register (`/Circuit/References/warranty_register.xlsx`).
3. Compare the install date against the warranty term for that model.
4. Report coverage status and, if expired, the expiration date.

If the serial number is not in the register, say so explicitly rather than guessing.
Keep the instructions focused on this one task. The agent already has its core instructions; the skill only needs to cover what makes this task different.
4

Attach reference files (optional)

Use the Files area to attach any small reference documents the agent should have on hand when running this skill: a lookup table, a checklist, a template, an internal glossary. You can drag and drop files or click to browse.Files attached to a skill are scoped to that skill. They don’t go into an index and they aren’t searched by the agent’s general search tool. The agent reads them directly when it’s applying the skill. This makes them well suited for small, stable references. For large or frequently updated content, use a regular index instead.
5

Save Skill

Click Save Skill to add it. The skill takes effect immediately; users chatting with the agent will see the new behavior on their next message. Click Cancel to discard.

​
Writing good skill instructions

A skill is a prompt that the agent applies selectively. A few patterns that work well:
  • Lead with when to use it. The first line or two should make clear what kind of question triggers the skill. Agents pick skills based on the overall instruction, so ambiguous openings lead to skills that never fire or fire at the wrong time.
  • Be explicit about steps. If the task has a sequence, number the steps. Tell the agent which tool to use at each step (“look up in warranty_register.xlsx”, “search the compliance index”, “ask the user for confirmation before proceeding”).
  • Say what to do when stuck. Tell the agent what to do if a lookup fails, a field is ambiguous, or the user’s question doesn’t match the skill after all. “Say you couldn’t find it” is better than letting the agent guess.
  • Reference attached files by name. If you attached warranty_register.xlsx, refer to it by that filename in the instructions. The agent will know to consult it.

​
Editing and removing skills

Click a skill’s row to expand it, change the instructions or files, and click Save Skill. The trash icon on the row header removes the skill entirely. Removing a skill takes effect immediately on the next chat message.

​
Tips

Test the skill in a fresh chat. Skills only apply when the agent recognizes the task, so open a new chat and phrase a realistic question. If the agent doesn’t pick up the skill, tighten the “when to use” line at the top of the instructions.
  • Keep one skill per task. A skill that tries to handle warranty lookups, RMAs, and service scheduling will fire inconsistently. Split them.
  • Version skills in the name when they change meaningfully. If you rewrite a skill’s procedure and want the team to know, update the name or note the date at the top of the instructions.
  • Use skills for structure, not only behavior. Breaking behavior into well-named skills makes the agent easier to maintain than stuffing everything into the core instructions.