> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills

> Create reusable AI instructions for customer research, meeting preparation, notebooks, Plays, and workflows.

A Skill saves instructions and selected tools so your team can reuse a consistent approach to a customer task. For example, a renewal review Skill can ask Quivly to gather account evidence, identify risks, and produce a brief with sources and open questions.

Manage Skills under **Configuration → Skills**. Search the library or filter by **All statuses**, **Published**, or **Draft** to find the Skill you need.

Each Skill has an editable draft and, once published, an active version. You can keep improving the draft while the published version remains available to use.

## Create a Skill

Select **+ Skill** in the library, then choose how to start:

| Option | When to use it | What happens |
| - | - | - |
| **Create from scratch** | You already know the task and instructions | Enter a name and open an empty draft |
| **Create from a template** | You want a starting point for a common customer task | Preview the template's instructions and tools, then choose **Use template** to create an editable draft |
| **Create with AI** | You want help turning an outcome into instructions | Describe the task, answer any follow-up questions, and review the generated draft |
| **Import from GitHub** | Your team maintains Skills in a repository | Follow the [GitHub import guide](/developers/github-skill-import) to choose and adapt a Skill |

Templates cover work such as sales handoffs, QBR preparation, onboarding, renewal reviews, and churn save plans. Customize the draft for your team's process before publishing it.

Creating a draft does not make it available to run. Complete its instructions, choose tools, and publish it when ready.

## Write the instructions

Describe the task clearly enough that someone else on your team could use the Skill with a different customer. Include:

* The customer, company, or other inputs the user should provide.
* The evidence to gather and the questions to answer.
* The structure and level of detail of the output.
* How to handle missing information and which claims need sources.

For example, a renewal review Skill could use these instructions:

```text theme={null}
Prepare a renewal review for the customer provided by the user.

Review the customer's contract dates, revenue, health, usage,
recent conversations, and support issues where available.

Return:
1. A short account summary.
2. Renewal risks, with supporting evidence and source links.
3. Open questions and information that is missing.
4. Suggested next steps for the account owner to review.

Keep observed facts separate from your interpretation.
Do not treat missing usage or revenue data as zero.
```

Use the **Skills Agent** in the editor to help draft or refine the instructions. Review its proposed changes and accept or discard suggestions before saving or publishing.

Skill names can contain up to **64 characters**, and instructions up to **50,000 characters**. Use a short, recognizable name so teammates can find it in the Skill picker.

## Choose tools

Tools provide the information the Skill needs. In the editor's **Tools** panel, search for a group or app, open its details, and turn on individual tools or the whole group.

Available choices include Quivly customer data, connected apps, external MCP tools, and built-in company and people research. The list depends on the connections and tools available to your workspace.

<Steps>
  <Step title="Start with the evidence your task needs">
    For a renewal brief, choose tools for customer information, revenue, health, usage, conversations, and support as needed. Select tools that answer the questions in your instructions.
  </Step>

  <Step title="Review suggested tools">
    After writing the instructions, select **Suggest tools** to get recommendations. Review and accept the recommendations you want; requesting suggestions does not change your selection automatically.
  </Step>

  <Step title="Check connected apps and research tools">
    If the task needs information from another app, check that the relevant connection is available. For public company profiles, stakeholder discovery, hiring, and technology research, use **Company and people research**. See [Quivly Enrichment](/integrations/agent-tools/quivly-enrichment) for examples.
  </Step>
</Steps>

Selected tools affect execution differently depending on where the Skill is used. Workflow Skill steps and Plays use the configured tool selection; only tools supported for that step can run. Ask Quivly, notebooks, and Meeting Prep use the Skill's instructions with their broader available research tools. Selecting a Skill does not grant access to disconnected apps or authorize a proposed action.

## Save and publish

Use **Save draft** to keep your edits without changing the version teammates use. Saving a draft is useful while you are still refining instructions or reviewing tool choices.

<Steps>
  <Step title="Review the draft">
    Check the instructions and selected tools. Publishing requires instructions and at least one tool. Resolve pending AI suggestions first.
  </Step>

  <Step title="Publish the first version">
    Select **Publish**. Quivly saves any unsaved edits before opening the publication confirmation. Add an optional change note and confirm publication.
  </Step>

  <Step title="Publish later changes">
    Edit the Skill's draft, then select **Update** and confirm when you want the new version to become active. The previous published version remains active until the update is published.
  </Step>
</Steps>

Publishing saves a version snapshot that you can inspect in version history. Each published Skill has a slash command, such as `/renewal-review`, for use in Ask Quivly. Command names must be unique in your workspace.

If the draft matches the published version, **Update** is disabled because there is nothing new to publish. Use the editor's reset control to discard unsaved changes when needed.

## Versions, duplication, and deletion

### Review or restore a version

Open **Version history** in the editor to see published versions and their change notes. Expand a version to review changes to its instructions, tools, name, description, or command.

To reuse an earlier version, select its restore control and confirm. Restore copies that version's **instructions and tools** into the current draft and replaces unsaved edits. Review the restored draft, then select **Update** to make it active. Restoring alone does not change the published version.

### Duplicate a Skill

Open **Skill Settings** and choose **Duplicate** to create a separate draft from the Skill's latest saved content. Save any edits you want to keep before duplicating.

The copy has its own publishing history and does not inherit the original slash command. Give it a suitable name, review its instructions and tools, and publish it separately.

### Delete a Skill

In **Skill Settings**, select **Delete** and confirm. The Skill and all its versions are removed from use, and it can no longer be invoked. Check any workflows or other configurations that depend on it before deleting it.

## Where Skills are used

| Feature | How to use a Skill | What to know |
| - | - | - |
| [Ask Quivly](/product/ask-quivly) | Type **/** or use the Skills menu | The Skill's instructions guide the conversation; Ask retains its broader available tools |
| [Ask Quivly in Slack](/product/ask-quivly-slack) | Use an explicit Skill command in your request | Follow the Slack guide for supported commands and interaction behavior |
| [AI notebooks](/product/notebooks) | Select a Skill in **Write with AI** or through the editor's slash command | The Skill guides the generated content; review the result before using it |
| [AI fields](/product/ai-fields) | Select **Use a skill** in the field setup | Instructions are copied and selected tools are added to the field's existing selection; edit the field independently afterward |
| [Agent workflows](/product/agents) | Choose a Skill for a **Skill** step | The step uses configured tools to investigate or produce an output; action steps handle subsequent changes |
| [Plays](/product/plays) | Select a published Skill for the Play's investigation | The Play uses the current published Skill to investigate; proposed actions follow the Play's separate review and execution process |
| [Meeting Prep](/customer-views/communications-tab) | Choose published Skills in the Meeting Prep configuration | Briefs use current published versions; one selected Skill is used directly, while several allow Quivly to choose a suitable one |
| [Quivly MCP](/developers/mcp-server) | External AI clients discover and read Skills, including for notebook generation | Use the MCP guide for connection and supported operations |

AI fields keep a copy of the instructions and tools loaded during setup. Publishing a newer Skill version does not automatically update that field's copy.

Meeting Prep can use a general brief when no suitable Skill is selected or Skill-based preparation cannot complete. Calendar setup, eligible meetings, and delivery options are explained in [Communications](/customer-views/communications-tab).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Why can't I publish the Skill?">
    Add instructions and select at least one tool. Accept or discard pending AI suggestions, then try again. If a command name is already in use, choose a different one in Skill Settings. If publication reports an unavailable or invalid tool, review the selected tools, restore the required connection where appropriate, or remove and replace the tool.
  </Accordion>

  <Accordion title="What does Saved but unavailable mean?">
    A previously selected tool is no longer available. Quivly keeps the selection so you can review it. Read the explanation beside the tool, then restore its availability or select **Remove** and choose a suitable alternative. Adjust the instructions if the task can no longer retrieve the same information.
  </Accordion>

  <Accordion title="What happens if the tools fail to load?">
    Your saved choices are kept. Select **Retry** to load the list again. A loading error does not mean the Skill's tool selection has been cleared.
  </Accordion>

  <Accordion title="Why are my edits not appearing when the Skill runs?">
    Check whether you saved a draft without publishing it. Select **Update** and confirm to activate the revised version. If you copied the Skill into an AI field, update the field's own instructions and tools as well.
  </Accordion>

  <Accordion title="Does choosing a Skill approve changes to customer data?">
    Skill selection provides instructions and research configuration. Action proposals, approvals, and execution depend on the feature where the Skill runs. Review proposed changes through that feature's action flow; a selected Skill alone does not approve them.
  </Accordion>

  <Accordion title="Can I edit an imported Skill?">
    Yes. Review and adapt its draft in the editor, including its tool selection, before publishing. See [Import Skills from GitHub](/developers/github-skill-import) for source refresh behavior and [Skill format](/developers/skill-format) for repository authoring.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.