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

# Skills

> Turn your team's procedures and rules into skills agents apply on their own in Chat, Review, Incident, and Assessment.

A skill is a written procedure or set of rules, stored as a `SKILL.md` file, that agents follow when the task in front of them matches it. Write your triage steps, review checklist, or naming convention once, and agents apply it without you repeating it in every prompt.

## When to use a skill

One test decides it: if agents should follow it step by step, make it a skill. If they should look things up in it, put it in a [knowledge base](https://docs.cloudthinker.io/guide/knowledge.md). A "check CPU, then credits, then traffic" triage runbook is a skill. A 40-page vendor manual or a service inventory goes in a knowledge base.

| | Skill | Knowledge base |
| - | - | - |
| Holds | Procedures and rules agents follow | Documents and websites agents search |
| Examples | Step-by-step triage runbook, review checklist, tagging policy | Architecture docs, vendor manuals, past postmortems |
| Changes | How the agent works | What the agent knows |
| Format | A `SKILL.md` file, written in CloudThinker or uploaded in a `.zip` | Uploaded files or crawled websites |

A skill can point agents at a knowledge base document, so the two work well together. Skills are one of several surfaces that hold the context you give CloudThinker; [Teach CloudThinker](https://docs.cloudthinker.io/guide/teach-cloudthinker.md) compares all of them.

## How a skill gets used

A skill is used only when all three are true:

1. **It is enabled.** The switch on the skill is on. New skills start enabled.
2. **It is available on the surface.** The surface where the work happens is ticked under **Available in** (see the table below). New skills start with **Chat** only. This applies to `/` too: the `/` menu lists every enabled skill, but chat can't use one without **Chat** ticked, and the agent carries on without it. Tick **Chat** on any skill you plan to run by name.
3. **It fits the task.** On every surface, including Review, the agent sees only the skills available there and loads the ones whose name and description match the work. It can load several skills for one task. So write the description in the words of the request. Bad: "CPU stuff". Good: "Investigate high CPU or a slow EC2 instance".

| Surface | Where it runs |
| - | - |
| **Chat** | Workspace chat, plus runs with no surface of their own, such as automations and webhooks |
| **Review** | Merge request and pull request reviews in [Review](https://docs.cloudthinker.io/guide/code-review/overview.md) |
| **Incident** | Incident analysis and root cause in [Resolve](https://docs.cloudthinker.io/guide/incident/overview.md) |
| **Assessment** | Well-architected and posture assessments |

You can also run a skill by name: type `/` in the chat prompt box and pick it from the menu. When an agent uses a skill, its activity shows a **Load Skill** step.

CloudThinker also publishes ready-made skills in the [Skills Hub](https://www.cloudthinker.io/skills). An installed hub skill becomes a workspace skill you manage like your own, and it doesn't change when the hub version does. To install one, see [custom skills](https://docs.cloudthinker.io/guide/skills/custom-skills.md#create-a-skill).

A new workspace's skills list starts empty. CloudThinker's built-in skills, such as `pdf`, `docx`, `pptx`, `xlsx`, and `deep-research`, work without setup. They don't appear in the list, so you can't edit or turn them off. Their names are reserved: your own skill can't use one.

## Who can do what

In **More → Workspace settings → Skills**, only workspace **Admins** can create, edit, attach, or delete skills, including turning the switch on or off and changing **Available in**. Developers can see the skills list and run skills with `/`. Viewers can see skills but can't chat, so they can't run them. See [roles](https://docs.cloudthinker.io/guide/security/roles.md).

> [!NOTE]
>
> Three paths add a skill without an Admin, and each one goes live in **Chat** for every agent:
>
> * **Skills Hub install.** The install doesn't check the workspace role. Any member who opens a hub skill's install link from the [public catalog](https://www.cloudthinker.io/skills) can install it into their current workspace.
> * **`/create-skill` in chat.** Any member who can chat can run it, and the agent writes the skill itself.
> * **[Learning Mode](https://docs.cloudthinker.io/guide/agents/customize.md#learning-mode).** A custom agent on **Auto** or **Offer** saves skills from chat. [Audit Logs](https://docs.cloudthinker.io/guide/security/audit-logs.md) don't record these. Set it to **Off** if every skill should come from an Admin.
>
> Check **More → Workspace settings → Skills** from time to time. An Admin can turn off, re-scope, or delete any of these skills there.

## Ways to create a skill

| Method | Best for |
| - | - |
| **Create with CloudThinker** | A first skill: CloudThinker interviews you and drafts the file |
| **Write skill instructions** | Rules you already know: a form with name, description, and instructions |
| **Upload zip file** | Skills you keep in a repository, or skills with scripts and reference files |
| **Browse Skills Hub** | Ready-made skills from CloudThinker |

[Custom skills](https://docs.cloudthinker.io/guide/skills/custom-skills.md) has the steps. For the file itself, see [Skill format](https://docs.cloudthinker.io/guide/skills/skill-format.md).

## Next steps

> [card] [Custom skills](https://docs.cloudthinker.io/guide/skills/custom-skills.md)
>
> Write effective skills and attach them to Review, Incident, and Assessment

> [card] [Skill format](https://docs.cloudthinker.io/guide/skills/skill-format.md)
>
> Learn the SKILL.md structure with a complete worked example

> [card] [Custom agent quickstart](https://docs.cloudthinker.io/guide/agents/quickstart.md)
>
> Pair a skill with a custom agent and test it end to end

> [card] [Knowledge base](https://docs.cloudthinker.io/guide/knowledge.md)
>
> Give agents documents and websites to look things up in


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