Skip to main content

Skills

A skill is a reusable capability package that bundles together instructions, tools, and knowledge sources into a single unit. Instead of manually configuring the same tools and prompts on multiple agents, create a skill once and attach it to any agent.

Why Use Skills?

Think of skills like job training modules. A “Calendar Management” skill includes the Google Calendar tool, booking instructions, and availability-checking knowledge. Attach it to any agent and they instantly know how to manage calendars. Benefits:
  • Reusability — Create once, use across many agents
  • Consistency — All agents with the same skill behave the same way
  • Modularity — Mix and match skills to build capable agents
  • Easy updates — Update a skill and all agents using it get the improvement

Skill Structure

Creating a Skill

From the Dashboard

  1. Navigate to your agent’s Skills tab.
  2. Click Create Skill.
  3. Fill in the skill details:
    • Name and description
    • Select tools to include
    • Add instructions (these are appended to the agent’s main instructions)
    • Attach knowledge sources
  4. Click Save.

Via the API

Response

Attaching Skills to Agents

From the Dashboard

  1. Go to your agent’s Skills tab.
  2. Browse available skills.
  3. Click Attach on the skills you want.
  4. Set the priority (higher priority skills are applied first).
  5. Optionally override skill configuration for this specific agent.

Via the API

Detach a Skill

Managing Skills

List Available Skills

List Skills on an Agent

Update a Skill

Delete a Skill

Deleting a skill automatically detaches it from all agents.

Skill Priority

When multiple skills are attached to an agent, priority determines the order in which their instructions are injected into the agent’s context:
  • Priority 0 (default) — Applied first
  • Priority 1 — Applied second
  • Higher numbers = lower priority
If two skills provide conflicting instructions, the higher-priority skill takes precedence.

Public Skills

Skills can be made public to share them across your organization or with other users:
  • Private skills (default) — Only visible to you
  • Public skills — Visible to all users in your organization
Set is_public: true when creating or updating a skill.

Example Skills

Web Research

Email Management

Data Analysis

Best Practices

  • One skill per capability — Don’t bundle unrelated tools into one skill.
  • Write clear instructions — The skill’s instructions should be self-contained and specific.
  • Use descriptive names — “Invoice Processing” is better than “Finance Skill.”
  • Test skills individually — Verify the skill works on a test agent before rolling out.
  • Version through updates — When updating a skill, all agents using it immediately get the new version.