Skills
A skill packages knowledge the agent shouldn't have to be told in every task: a procedure, a document format, a policy, a voice. Enable a skill on a project and every task can use it — the agent sees a short header for each enabled skill and loads the full body only when the task actually calls for it, so a project can carry many skills without drowning the agent in instructions.
What's in a skill
| Field | Purpose |
|---|---|
| Title & key | How the skill is identified and referenced |
| Description | The one-liner the agent uses to decide when to open the skill — write it as a trigger condition |
| Prompt body | The full instructions: steps, formats, rules, examples |
| Tags | Organization and discovery |
Skills come from the gallery or are written by you; each project enables its own set and controls their order.
What makes a good skill
The description decides whether the skill gets used — make it say when, not just what:
❌ "Contract review guidelines" ✅ "Use when reviewing any contract, NDA, or vendor agreement — clause checklist and risk labels"
The body should be the document you'd hand a new hire:
# Contract Review
When reviewing a contract:
1. Extract parties, term, renewal, termination, liability cap, governing law.
2. Compare each clause against our standard positions below.
3. Label every clause GREEN (standard), YELLOW (negotiable deviation),
or RED (unacceptable — must escalate).
4. Output: a table of clauses with labels and a one-paragraph
recommendation. Never advise signing — recommend and escalate.
Our standard positions:
- Liability cap: 12 months of fees ...
- Auto-renewal: must have 60-day opt-out ...Common skill archetypes
- Procedure skills — "how we do X": review checklists, triage steps, escalation rules.
- Format skills — "what our X looks like": report layouts, memo structure, slide conventions.
- Voice skills — writing style distilled from your existing documents, so drafts sound like your team.
- Policy skills — the rules the agent enforces: spend policy, brand claims, data handling.
- Domain packs — per-specialty variants (an employment-law skill vs. a commercial-law skill on the same legal project).
Skills + templates + automations
Skills define how, templates define what, automations define when. A complete workflow is usually all three: a webhook creates a task from a template, and the template's work leans on the project's skills.