Skills

A skill is packaged know-how: instructions, templates, and supporting files that teach the agent how to do a kind of work well. Connections give agents access to your tools; skills make the output come out your way. Every agent ships with built-in skills for common deliverables — generating PDFs, building spreadsheets, analyzing data. Your project can add its own on top.

​

When to create a skill

Create a skill when you catch yourself re-explaining the same thing across conversations:

• A format — “our weekly report always has these five sections, in this order, with this cover.”
• A procedure — “to close a support case, check these three systems in this sequence.”
• Company assets — the letterhead, the presentation template, the tone guide for proposals.

Once it’s a skill, every agent that has it produces the work consistently — no re-explaining, no drift between conversations.

​

Using skills

A skill can be enabled on multiple agents, and an agent can have many skills. Enable them on the agent alongside its connections; the agent draws on the relevant skill when the task calls for it.

​

Skills don’t grant access

A skill teaches; it never unlocks. Adding a skill gives the agent no new access to external tools — reaching your CRM or Stripe always goes through a connection and its permissions. A skill that says “email the report to the client” still results in an approval request if that’s what the connection’s rules require.