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

> ## Agent Instructions
> The docs are served at https://docs.devias.io. Every path in these docs is relative to that root: /llms.txt is https://docs.devias.io/llms.txt.
> Devias is an open-source platform that works as an operating system for a business: a core (records, views, workflows, agents, permissions) with installable modules.
> Pages are typed by folder. concepts/ explains what things are, guides/ gives procedures, reference/ is exhaustive (SDK, CLI, HTTP API), operate/ covers hosting. Use /start/glossary for exact terms.
> Every id in a module (module, object, field, view, action, workflow, step, connection, variable, event, policy) is a uuid. Generate them with `devias id <count>`. Never invent dotted or readable ids.
> Run `devias plan` and read its output before `devias apply`. Apply only what the plan says.
> The OpenAPI document, including the routes of the modules in the reference setup, is at /reference/api/openapi.json.
> Devias is young and changes quickly. If a page and the source repository (github.com/devias-io/devias) disagree, the repository is right.

# Skills

> How to write and use skills. A skill is a procedure written once, with a label, a one-line description the agent matches against, and a Markdown body. Explains why a skill is not an instruction, who can use a skill, and how module skills behave.

A **skill** is a procedure written once and used by any agent that needs it, for example "how we qualify a lead" or "how to close out a deal".

## Skill or instruction

An agent's instructions are read in every conversation. A skill is read only when it is relevant: the agent sees each skill's one-line description and loads the full text only when a request matches. This keeps conversations focused and allows as much detail as a procedure needs.

## Write a skill

Choose **Skills** in the sidebar and create one. A skill has three parts.

| Part | Meaning |
| - | - |
| `label` | The name people see. |
| `description` | One line saying when to use the skill. The agent matches requests against it. |
| `body` | The procedure, in Markdown. |

Write the body as numbered steps, and say what to do when something is missing.

```md theme={"dark"}
# Close out a deal

1. Set its stage to Lost.
2. Set its lost reason. Ask which one if you do not know; never guess.
3. Log a comment with what the person said about why.
```

## Who can use a skill

* A skill written in the workspace is available to agents given access to it, and to any agent that may use every skill.
* A skill that comes from a module belongs to that module. It updates with the module and is archived when the module is uninstalled. It can be switched off but not edited.

## Related

* [Define an agent](https://docs.devias.io/guides/agents/define-an-agent.md): give an agent access to skills.
* [Agents and skills in a module](https://docs.devias.io/guides/modules/agents-and-skills.md): ship them with a module.


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