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

# Skills

> Choose, edit, and create the playbooks daoco agents use while they work.

Skills are playbooks that daoco loads when a task matches them. They can define a writing method, a design process, a research checklist, or rules for working with a specific tool. Skills guide the work; they do not start runs on their own.

Open the brand switcher and choose **Skills**. The page has daoco's built-in **Library** and **Your skills** for workspace-owned playbooks.

The first time you open **Skills**, a five-step walkthrough explains the library, workspace skills, triggers, agent access, brand scope, and publishing controls. It switches between the two tabs for you but does not change any skill.

## Use the built-in library

Search the library by name, category, or purpose. Open a skill to read its instructions and see which agents can use it.

Workspace admins can turn a built-in skill on or off. Turning it off keeps it in the library but prevents agents from loading it. Choose **Edit** to create a workspace copy when the shipped instructions are close but not quite right. Once that copy is on, agents use it instead of daoco's version.

## Create a skill

<Steps>
  <Step title="Add the basics">
    Under **Your skills**, choose **New skill**. Give it a clear name and
    describe the tasks that should trigger it.
  </Step>

  <Step title="Choose where it applies">
    Select the agents that may load it. You can make the skill available to
    every brand in the workspace or limit it to selected brands.
  </Step>

  <Step title="Write the playbook">
    Add direct instructions in Markdown. Put examples, source material, or
    longer reference notes in the skill's extra files instead of crowding the
    main playbook.
  </Step>

  <Step title="Turn it on">
    New skills start off. Review the saved copy, then turn it on when agents
    should begin using it.
  </Step>
</Steps>

Published skills can only be changed by workspace admins. Other members can draft skills for an admin to review.

## Import and export

Use **Import** to add a compatible skill package. Export a workspace skill when you want a backup or need to move it to another workspace. Imported skills still start off, so nothing changes agent behavior until someone enables them.

## Write a useful trigger

The **When to use** field decides whether daoco considers the skill for a task. Name the situation and the expected work. Avoid broad triggers such as "use for marketing" because they make unrelated requests compete for the same playbook.

Good trigger:

> Use when writing a customer case study from an interview transcript. Pull only claims supported by the transcript and keep direct quotes attached to the named speaker.

Keep the playbook concrete. Tell the agent what inputs to check, what decisions to make, what output to return, and what it must not invent.

## Manage a skill

* Turn a custom skill off to stop agents loading it without deleting the draft.
* Archive a custom skill when the workspace no longer needs it. If it replaced a built-in skill, archiving restores daoco's version.
* Edit the workspace copy rather than the built-in original. Library updates remain separate from your copy.
* Limit a specialist playbook to the agents that can act on it. A video editing checklist does not need to load during billing questions.

Skills load only when they match the current task. They do not appear as transcript steps. The work they guide remains visible in the normal [chat execution view](/core-workflows/workflow-panels#execution-ledger).