Skills: reusable playbooks

Some jobs need detailed, step-by-step know-how: "how we write a weekly client report", "how we qualify a lead". Putting all of that in an agent's instructions makes them long, and the agent reads them on every task. A skill solves this.

A skill is a small folder with a main file, SKILL.md, holding a name, a description and the instructions. It can also contain:

• references/: longer documents the agent reads only when needed.
• assets/: templates and files, such as a report layout.
• scripts/: small programs the agent can run in its sandbox (its private workspace, covered later).

Agents only see each skill's name and description at first. When a request matches, they load the full skill. So write descriptions that say clearly when to use it.

Ways to create a skill: Create With AI (a guided chat), Write Skill Instructions (a simple form), Upload Files, or Add Existing Skill. Names are lowercase with hyphens, such as weekly-client-report.

With AI Skill Editing turned on, an agent can create and improve skills itself: when you correct it ("always include the churn number"), it can update the skill so the lesson sticks. The Edits tab shows the history of changes.

Skills can be shared with roles: Owner, Editor, Viewer, and Use Only (can use it, can't see inside). Admins can publish organisation-wide skills.

Note: attaching a skill doesn't grant app access. The agent still needs the right connectors.