Skills

A skill is a reusable piece of instructions the agent can load on demand. Think of it as a named prompt — a playbook, a recipe, a style guide, or a complex procedure you don't want to re-explain every time.

Skills are scoped to an org, so any project in that org can use them.

When to use skills

• You have a repeated workflow ("how to triage incoming support tickets").
• You have a style guide ("how we write customer emails").
• You have a multi-step procedure that's too long to paste into every chat.
• You want to share institutional knowledge across team projects without re-typing it.

If instructions only apply to one project, consider putting them in the project's instructions field instead (see Organizations & Projects). Skills are for things that are broadly reusable.

How the agent uses them

Skills aren't loaded automatically — the agent reads them when it needs to. It can:

• Search for a relevant skill by topic or keyword.
• Read the full body of a skill it finds useful for the current task.

You can nudge the agent to use a specific skill ("use the customer-support skill") or trust it to find one on its own.

Creating and editing

Skills live in the org settings (or you can ask the agent to create one for you). Each skill has:

• Name — short, searchable (e.g. customer-support, migration-playbook).
• Description — one line so the agent knows when to reach for it.
• Body — the actual instructions. Markdown is fine.

The agent can create and update skills too — useful for capturing what you've taught it across conversations.