Skip to main content
A skill is a saved recipe for the AI: instructions (what to produce and how) plus a tool allowlist (which data it may read). Write it once, and your whole team gets the same QBR prep, renewal risk read, or health digest every time. Manage skills under Settings → AI → Skills.

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-name in Ask Quivly.
  • Duplicate forks a skill; Archive retires it.
Publishing requires instructions and at least one tool. Names are 1–2 words; instructions up to 10,000 characters.

Where skills run

SurfaceHow
Ask Quivly/ slash command or the Skills menu
NotebooksWrite with AI and the editor slash command
AI fields”Use a skill” copies its instructions and tools into the field
AgentsThe Skill step runs one inside a workflow
MCPExternal AI tools list skills and use them to generate notebooks

FAQ

No — skill tools are read-only. Write operations happen through agent action steps, not skills.
Editing continues on a draft; the published version keeps running until you publish again. To fork a different direction, use Duplicate.