> ## Documentation Index
> Fetch the complete documentation index at: https://player-zero-slack-mcp-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills

> Package reusable expertise as Skills your team can discover, share, and apply to any piece of work.

## What Are Skills?

Skills are reusable packages of expertise that standardize how your team works with PlayerZero. A Skill is more than a single prompt: it can be a folder of files, with a main set of instructions alongside any supporting material such as references, templates, and scripts.

Skills were previously called Playbooks. Everything you built as a Playbook carries over, and the library, categories, and version history work the same way.

<Note>
  A Skill can be applied three ways: referenced from a workflow stage, invoked directly with a slash command, or selected by PlayerZero when it judges the Skill relevant to the task at hand.
</Note>

***

## Creating a Skill

Navigate to **Organization Settings → Playbooks & Skills** to manage your library, then choose how to start:

<AccordionGroup>
  <Accordion title="From Scratch">
    Create a new Skill with a blank editor and write the instructions yourself.
  </Accordion>

  <Accordion title="From a .zip File">
    Import a Skill from a `.zip` archive. This is how you bring in agent skills authored in other tools, or move a Skill between organizations. Skills you export are packaged the same way, so an exported archive can be re-imported anywhere.
  </Accordion>

  <Accordion title="From a Thread">
    If you like how PlayerZero handled something, turn that work into a Skill directly:

    1. Hover over an assistant response to reveal the **Create skill** action
    2. PlayerZero drafts a Skill definition from the response and shows it as a card in the chat
    3. Review the generated title, description, instructions, and category
    4. Save to open the creation form pre-filled with the generated content
  </Accordion>
</AccordionGroup>

### Skill Fields

| Field            | Description                                                  |
| ---------------- | ------------------------------------------------------------ |
| **Title**        | A short name for the Skill (unique within your organization) |
| **Description**  | A brief explanation of when and why to use this Skill        |
| **Instructions** | The guidance applied when someone uses the Skill             |
| **Category**     | Organize by type. See the category list below.               |
| **Tags**         | Custom labels for filtering and search                       |

### Categories

Categories come from a fixed set shared across job roles, workflows, knowledge groups, and Skills:

Documentation, Engineering, Product, Design, SRE, Quality Assurance (QA/QE), Data Science, Go To Market/Sales, Marketing, Support, and Other.

***

## Using a Skill

<AccordionGroup>
  <Accordion title="Slash Command">
    * Type `/` in the chat input to open the Skills overlay
    * Browse or search for the Skill you want
    * Use **↑↓** to navigate and **Enter** to select
    * The Skill is applied to your message — add your own context on top
  </Accordion>

  <Accordion title="Skills Library Button">
    * Click the library icon next to the chat input
    * Browse by category or search by title, description, or tag
    * Select a Skill to attach it to your message
    * The selected Skill appears as a tile below the input
  </Accordion>

  <Accordion title="Workflow Stage Instructions">
    * Type `/` in the stage **Instructions** field when creating or editing a workflow stage
    * Browse or search for the Skill you want
    * Select it to insert its instructions into the stage
    * This standardizes agent behavior across stages — see [Configuring Workflows](/features/configuring-workflows)
  </Accordion>

  <Accordion title="Selected by PlayerZero">
    PlayerZero can reach for a Skill on its own when it judges one relevant to the task, so shared expertise gets applied even when nobody remembers to invoke it.
  </Accordion>
</AccordionGroup>

When you submit a message with a Skill attached, the Skill is combined with your message and sent together. The chat shows a label naming the Skill that was applied, and you can preview it inline or open it in a full dialog.

***

## Managing Skills

From **Organization Settings → Playbooks & Skills**, you can:

* **Create** new Skills
* **Edit** existing Skills — update the title, description, instructions, category, or tags
* **Fork** a Skill to create a variant without modifying the original
* **Delete** Skills you created (or any Skill if you have owner permissions)
* **Search** across titles, descriptions, and tags

Because the library is shared at the organization level, a Skill one person writes becomes something the whole team can discover and apply to shared work.

### Sorting

Use the sort dropdown to change the order of your list:

* **Recently updated** (default) — Skills with the most recent edits appear first
* **Alphabetical** — Skills are sorted from A to Z

### Version History

Every edit creates an immutable version snapshot. To view a Skill's history, open its detail panel and click the **Version** badge to expand the version history.

Each version shows:

* The user who made the change
* When the change was made
* The version number

To restore a previous version, select it and confirm the restore. Restoring creates a new version with the restored content — it does not roll back or delete any history.

Viewing version history requires the **viewer** role. Restoring a version requires the **editor** role.

***

## Get Started

👉 [AI Player overview](/features/ai-player)

👉 [Setup guide](/developer-guide/quickstart-guide)