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

# Skill files

> Teach the agent a repeatable procedure with one Markdown file: a name, when it applies, and what to do.

## What a skill is

A skill is a saved procedure the agent follows: a **name**, a one-paragraph **description** of when it applies, and a Markdown **body** of instructions. Every turn’s prompt lists the available skills by name and description; the agent loads a fitting skill’s body before a task, and you can ask for one directly. Invoking a skill never runs code or grants credentials, network or permissions: the body is guidance, not authority.

Skills come from two places. **Platform** skills ship with the release, read-only. **Personal** skills are yours, saved on the outpost, up to 128 per account. A personal skill with the same name as a platform skill overrides it for you alone.

## Use a skill

Type `/` in the console composer or the terminal workspace and pick one; the menu filters as you type and `Tab` or `Enter` inserts `/name`. A message that starts with `/name` invokes that skill for the turn; `/name` alone tells the agent to carry it out as written. When the agent loads a skill itself, the transcript shows *Pulled Name* with the instructions it received; a message that starts with `/name` shows no such row, because the body arrives with the message.

```text Composer theme={null}
/pdf split uploads/brief.pdf into pages 1-3 and 4-end

/daily-sitrep
```

## Write one

In the console, open **Settings → Skills** and choose **New skill**: a **Name** of lowercase letters, digits and hyphens, a **Description** the agent reads to decide when to load it, and **Instructions** in Markdown with a preview. Opening a platform skill offers **Customize for yourself**, which makes a personal copy under the same name. Analysts and above can write skills; viewers read them.

You can also ask the agent in chat, for example *save this as a skill called daily-sitrep*. It creates, updates, renames and deletes personal skills only when you ask, and a save is durable at once, across conversations and restarts.

As a file, a skill is `SKILL.md`: a frontmatter block with exactly `name` and `description`, then the body. Limits are 64 characters for the name, 1,024 for the description and 64 KiB for the body.

```markdown SKILL.md theme={null}
---
name: daily-sitrep
description: "Draft a daily situation report from the operator's notes. Use for /daily-sitrep, a sitrep, or an end-of-day summary."
---
# daily-sitrep

1. Ask for the period covered only if the notes do not say.
2. Group the notes under Situation, Actions, Issues and Next 24 hours.
3. Keep each fact's source and time, and name what is missing.
4. Return the report as Markdown in the reply.
```

> [!NOTE]
>
> Quote the description so a colon in it does not break the frontmatter. Keys other than name and description are refused by the platform loader and dropped by the terminal importer.

## Import from the terminal

In the terminal workspace, `/skills` lists, opens, uses and deletes your skills, `/skill-create` writes a new one in a form and `/skill-import` reviews a local `SKILL.md` and saves it as a personal skill. Files up to 128 KiB are accepted; the 64 KiB body limit still applies.

```text Terminal workspace theme={null}
drkm                               # opens the workspace
/skill-import ~/skills/daily-sitrep/SKILL.md
/skills
/daily-sitrep from today's notes
```

## What ships with the platform

Each release carries a set of platform skills. Among the general-purpose ones: `docx`, `pdf`, `pptx` and `xlsx` for reading and writing office documents on the agent’s computer, `memory` for the mesh’s shared notes, and `walking-routes` and `driving-routes` for route planning on the map. Mission-specific skills for the Overwatch and Splash apps ship beside them. A skill tied to a capability ships only where the deployment runs that capability. A few select a library of tools for the agent’s computer when invoked.

For programs, the same catalog is an HTTP API on the outpost: `GET /users/me/skills` lists it, `POST /users/me/skills` creates a personal skill, and `PUT` and `DELETE` on `/users/me/skills/{name}` replace and remove one, with a session or an API key.


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