Skip to main content
Skills are named instruction blocks that live in skill packs. Each skill tells the agent what to do in a specific situation, without rewriting the main system prompt. Use skills when the same behavior should apply across agents — introductions, refund handling, escalation rules, FAQs. Edit once in the pack; every agent that has that pack attached picks up the change.
Open Agents > Skills in Agents Platform. Skills live in skill packs. Agents attach packs, not individual skills. Import and Export are available on an installed pack’s page, not on template cards.
Agent Skills page

​
Mental model

Skills and packs are workspace-scoped. Enable or disable happens per skill, not per pack. Attaching a pack gives the agent every enabled skill in that pack.

​
Browse packs

On Agents > Skills:
  • All — installed packs in this workspace. Open a pack to manage its skills.
  • Templates — pre-built packs. Install a template to create an installed pack you can edit.
Create your own pack from the Skills page when you need a custom group (for example Support or Collections).

​
Create a skill

1

Open an installed pack

From Agents > Skills, open the pack that should own the skill.
2

Create skill

Select Create skill (top of the pack page).
3

Fill in the fields

Select Create skill. The skill appears in that pack.
You can also create a skill while browsing a template pack before it is fully installed; the form targets the template until an installed pack exists.

​
Edit, enable, or disable

From the pack’s skill list:
  • Open a skill to view or edit Name, Type, Situation, and Instructions.
  • Use the skill’s on/off control to disable it without deleting the definition. Disabled skills are omitted from the agent prompt until you turn them back on.
Template-derived skills can be edited; the product marks them dirty when they diverge from the template. Reset-to-default (when available on the skill) restores the template copy.

​
Import and export CSV

CSV import and export are scoped to one installed skill pack. The pack comes from the page you are on — not from a column in the file. Import and Export appear on the installed pack page only (hidden on uninstalled template cards and on the import wizard itself).

​
Export

  1. Open an installed pack.
  2. Select Export.
  3. Download skills-{pack-name}-{workspace-slug}.csv.
Export includes every skill in the pack (disabled and template-derived too).

​
Columns

Extra columns are ignored. Export uses this column order.

​
Import

  1. Open an installed pack and select Import.
  2. Upload a CSV (step: file).
  3. Map columns (step: mapping). Matching names are applied automatically; AI mapping may fill gaps. Common aliases such as instructions → instruction and whenToUse → situation are recognized.
  4. Review the preview (create / update / skipped, and optional deletes).
  5. Apply.

​
Row behavior

Creates are always user-owned. Import never creates packs. Blank optional cells overwrite on update.

​
Delete missing (off by default)

On the import flow, Delete missing skills hard-deletes user-created skills in this pack whose id is completely absent from the CSV. Not deleted: template-derived skills, and ids that appear in the file even if that row was skipped.
Delete missing cannot be undone from the import screen. Leave it off unless you intend a full replace of user-created skills in the pack.
Permissions: export needs skill.exportCsv; apply needs skill.applyImport. If Import or Export is missing, ask a workspace admin.

​
Attach skill packs to an agent

Agents attach skill packs, not individual skills. Open the agent → the skills / skill packs section on the agent configuration.
  1. Select Add Skill Packs.
  2. Choose one or more installed packs that are not already attached.
  3. Confirm Add Skill Packs.
The list shows each attached pack name and how many enabled skills it contributes. Use Remove to detach a pack from this agent (the pack and its skills stay in the workspace). If no packs are available to add, the empty state links to Manage Skills (Agents > Skills) so you can install or create a pack first. Attach skill in agent

​
Preview

  1. Open the agent → Preview → Test Agent.
  2. Run a conversation that should use a skill from an attached pack.
  3. If the behavior is wrong, return to the pack, edit or disable the skill (or detach the pack), and preview again.
Changes apply on the next conversation start. You do not restart the agent.

​
Place skills in the system prompt

Attached, enabled skills are injected into the agent’s system prompt by type. You control where each type lands with tags in the prompt. Supported tags (lowercase, exact):

​
How each type is written

  • FAQ and SOP — unlabeled situation: / instruction: lines. Skill names are not included.
  • General — instruction text only, starting on a new line. No situation: and no instruction: prefix.
Blank skills are skipped. A general skill with an empty instruction is skipped entirely.

​
Placement rules

  1. Tag present — The first @@skill.<type> is replaced with every attached, enabled skill of that type, in attachment order, padded with blank lines so it does not stick to neighboring text.
  2. Same tag twice — Only the first tag is filled. Later copies are removed.
  3. Tag with no skills of that type — The tag is stripped. Nothing is inserted.
  4. Unknown or misspelled tag — Tokens such as @@skill.foo or @@skill.FAQ are removed. Matching is lowercase and exact.
  5. Attached type with no tag — Those skills still run. They are appended at the end of the prompt in order: FAQ, then SOP, then general.
If the prompt has no skill tags at all, every attached type is appended at the end in that same FAQ → SOP → general order. Example:
With a refund FAQ attached, that becomes situation/instruction lines for the FAQ at the tag, then the rest of the prompt. Untagged general skills from attached packs still append at the end.

​
Practical notes

  • Prefer short, concrete instructions over long policy dumps.
  • Name skills so teammates can scan the list (FAQ – Billing, SOP – Escalate chargeback).
  • Group related skills in one pack; attach the pack to agents that need the whole set.
  • Put @@skill.faq / @@skill.sop / @@skill.general where that type should sit in the prompt; leave tags out only when end-of-prompt append is fine.
  • Export before a large import so you have a rollback file.
  • Disable instead of delete while experimenting.

​
FAQ

Do I attach skills or packs to an agent?
Packs. Add Skill Packs attaches whole packs. Enabled skills inside those packs are what enter the prompt. Can one pack be used by multiple agents?
Yes. Packs are workspace-level; attach the same pack to as many agents as you need. Do I restart the agent after editing a skill?
No. Skills are injected when a conversation starts, so edits take effect on the next run. What if I omit the @@skill.* tags?
Attached skills still inject. They append at the end of the prompt in FAQ → SOP → general order. Can I import into a template that is not installed?
No. Import and Export only show on installed packs. Does import create a new pack?
No. Rows always land in the pack whose page you opened. Will Delete missing remove template skills?
No. Only user-created skills whose ids are absent from the CSV are deleted when that option is on. Is there a public Skills REST API for CSV?
Not in this release. Import and export are Agents Platform UI (and workspace permissions) only.

​
Limitations

  • Agents attach packs, not individual skills. To give an agent one skill from a large pack, use a smaller pack or disable the skills you do not want.
  • Import/export is per installed pack — not workspace-wide in one file.
  • Invalid type values do not skip the row; they become general.
  • Ids that belong to another pack in the same workspace are skipped, not moved.
  • Skill names are not injected into the prompt. Types are not wrapped in markdown headings.
  • There is no public Skills CSV API in this release.
Questions: support@oration.ai or developers@oration.ai.