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

> ## Agent Instructions
> Enclave in these docs is the code and cloud security platform at enclave.ai. It is not Open Enclave, Intel SGX or other hardware enclaves, or enclave.gg.
> People use Enclave in the web app at https://app.enclave.ai or the desktop app. These docs describe no public Enclave API or CLI, so don't invent endpoints, commands, or config files.
> Connecting an integration needs a person to sign in and approve access in a browser. Tell the user the exact step to take instead of saying you completed it.

# Skills

> Save your team's repeated Research procedures as skills, then run one with /name or let Enclave pick it from its description.

A skill is a saved procedure, such as triaging findings by SLA or checking a deployment. Save the steps once, and anyone in your organization can run them in [Research](https://docs.enclave.ai/research/sessions.md) or [Slack](https://docs.enclave.ai/integrations/slack.md).

![The Skills list in Settings, showing each skill's /name, description, who updated it and when](https://mintcdn.com/enclave/yDTc_iq6XhSHDRMv/images/product/skills-list.png?fit=max\&auto=format\&n=yDTc_iq6XhSHDRMv\&q=85\&s=9b4790b8ce738e296966cdd1e0140e38)

## Who can manage skills

**Owner** and **Admin** can add, edit, and delete skills. So can a [custom role](https://docs.enclave.ai/admin/roles.md#custom-roles) with **Skill · Write**. Everyone else sees the list in **Settings → Skills** and can use any skill.

## Add a skill

1. Open **Settings → Skills** and click **New skill**.
2. Enter a **Name**, such as `triage-sla`. Use lowercase letters, digits, dashes, and underscores. People type `/triage-sla` to run it. A skill can't reuse a built-in command's name.
3. Enter a **Description** that says when to use the skill. Enclave reads it to decide when a request matches.
4. Write the **Instructions**: the steps Enclave follows. `$ARGUMENTS` is replaced by what someone types after the name. Without it, that text is added at the end.
5. Click **Create skill**.

![The New skill panel with a name, a description and instructions that use \$ARGUMENTS](https://mintcdn.com/enclave/yDTc_iq6XhSHDRMv/images/product/skills-new.png?fit=max\&auto=format\&n=yDTc_iq6XhSHDRMv\&q=85\&s=adcc5d8fdd653e8fe7def50e80fac486)

For example, with the instructions `List open findings past their SLA for $ARGUMENTS`, the message `/triage-sla payments repositories` lists the findings for the payments repositories.

## Use a skill

* **By name:** type `/` in the Research chat box. Your organization's skills appear after the built-in [slash commands](https://docs.enclave.ai/research/sessions.md#slash-commands). Pick one, add any arguments, and send. In Slack, write `@Enclave /triage-sla payments repositories`.
* **By description:** ask in your own words. When a request matches a skill's description, Enclave follows that skill.

![The Research chat box after typing /, with the organization's skills listed after the built-in commands](https://mintcdn.com/enclave/yDTc_iq6XhSHDRMv/images/product/skills-slash-menu.png?fit=max\&auto=format\&n=yDTc_iq6XhSHDRMv\&q=85\&s=0f2a740e4a28c44f51856a89190a1a93)

A skill doesn't change what Enclave is allowed to do. Each person's own [permissions](https://docs.enclave.ai/admin/roles.md) still apply.

## Edit or delete a skill

Click a skill in the list to change it, or click **Delete skill**. Sessions use the new version the next time they load the skill. After you delete a skill, Enclave no longer uses it.


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