What a skill is
Instructions for one kind of request, kept as a SKILL.md file with any reference files beside it. Only the name and description are always in the agent’s context; it reads the rest when a request matches.
Five skills are built in. Duplicate one, edit it, test it in chat, and your team’s way of reviewing a deal becomes the agent’s.
In early access today. The AI model isn’t switched on yet. Field updates come from built-in rules, which pick up only sentences that state a value outright. What works today
Instructions for one kind of request, kept as a SKILL.md file with any reference files beside it. Only the name and description are always in the agent’s context; it reads the rest when a request matches.
Each is a file you can open and read before you rely on it.
Built-in skills are read-only. Duplicate one to edit your own copy. Every save is a new version, and earlier versions are kept.
Test in chat runs the skill on a real request before your team depends on it.
A skill changes what the agent knows how to do, not what it is allowed to do. The Follow-up Email skill says it plainly: it never sends.
Enforced
A skill is text. The approval rules are code and database constraints, and they apply to every skill, built in or your own.
No. A skill changes what the agent knows how to do, not what it is allowed to do. Email is always a draft, and only a person approves.
A SKILL.md file with a name, a description and the instructions, plus any reference files it points to. The built-in Deal Review skill carries a MEDDPICC reference, for example.
Not in place. Duplicate it and edit your copy; the original stays as it was.
Run it with Test in chat on a real request, and compare with the earlier version, which is kept.
Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.
Early access. No payment details are asked for.