Creating a skill
Three paths: start from scratch, pick a template (eight built-in, covering post-sale, renewals, onboarding, health, and reporting — e.g. Sales Handoff Brief, QBR Prep, Churn Risk Assessment), or let AI generate one from a description. The editor includes an AI chat assistant that can draft the skill from your intent, edit instructions, suggest improvements, and browse or restore versions. Skills can read from ~20 data tools — customer profiles, contacts, calls, health scores, revenue, usage, insights, aggregations, and more. Developers can also import skills from GitHub in the Anthropic Agent Skills format.Lifecycle
- Draft → Publish — publishing makes the skill active and saves an immutable version snapshot. Version history shows diffs and supports restore.
- Each active skill gets a slash command name, so you can invoke it as
/skill-namein Ask Quivly. - Duplicate forks a skill; Archive retires it.
Where skills run
| Surface | How |
|---|---|
| Ask Quivly | / slash command or the Skills menu |
| Notebooks | Write with AI and the editor slash command |
| AI fields | ”Use a skill” copies its instructions and tools into the field |
| Agents | The Skill step runs one inside a workflow |
| MCP | External AI tools list skills and use them to generate notebooks |
FAQ
Can a skill change data?
Can a skill change data?
No — skill tools are read-only. Write operations happen through agent action steps, not skills.
Can I edit a published skill?
Can I edit a published skill?
Editing continues on a draft; the published version keeps running until you publish again. To fork a different direction, use Duplicate.
