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

# Publishing skills

> Write a skill as a folder on your machine and store a version of it from the to11 CLI; everyone who follows the project receives it.

You need the `to11` binary on your `PATH` and one run of `to11` to link your machine to a project — [Receiving skills](https://to11.ai/docs/skills/receiving-skills.md) covers both. For what a skill is, and why the browser reads them but does not write them, see [What a skill is](https://to11.ai/docs/skills/concepts.md).

## Write the folder

A skill is a directory whose entry document is `SKILL.md`:

```text theme={null}
incident-triage/
├── SKILL.md
└── references/
    └── paging.md
```

Write it yourself, or let a coding agent write it — **New skill** on the project's **Skills** page hands you a prompt to paste into one. Either way, the folder is what gets stored.

Stay inside the [limits](https://to11.ai/docs/skills/concepts.md#a-skill-is-a-folder-not-a-document): at most 128 files, 512 KB in any one file, 4 MB across all of them, UTF-8 text with `\n` line endings. A skill has no variables: `{{ … }}` is not substituted, and reaches the agent exactly as you wrote it.

## Store a version

```bash theme={null}
to11 skill store incident-triage --dir ./incident-triage --description "Triage an incident page"
```

Exactly one content source is required: `--dir` for a folder, `--from <file>` (or `-` for stdin) for a single file, `--body <text>` for inline text.

**A new skill needs a description, and the flag is one of two ways to give it.** Creating takes `--description` when you pass it and the entry document's frontmatter when you do not — with any content source, since `--from` and `--body` both become a `SKILL.md` too. Only an empty result is an error — or frontmatter that is not valid YAML, which is reported with its line and column. Quote a description that starts with `{` or `[`.

**Afterward the order reverses for a directory.** `--dir` takes the description from the entry document and reports the flag ignored, while `--from` and `--body` take it from the flag. So changing an existing skill's description through a directory store means changing it in `SKILL.md`; passing it on the command line will not. An entry document carrying no description changes nothing — the stored description stays as it was, without an error.

**Storing moves the skill's one label, `latest`,** to the new version. Everyone whose configuration follows `latest` — which is what `to11` sets up by default — receives it on their next sync; a machine pinned to a version keeps that version. **A store is a publish: do not store a work-in-progress version expecting it to stay private.** The version lands on this machine too — pass `--no-install` if you would rather it did not.

**A store writes no pin.** Your configuration follows `latest`, which is now the version you stored, so it receives later versions as everyone else does; an edit you make on disk is safe, because sync skips a skill you changed. A `version:` pin you already had is your hold, so it moves to the stored version, and `store` prints a `pinned` line naming the file — write `label: latest` in place of the `version:` there to follow `latest` again. If the entry picks its skills one by one, the skill is added to it as `{ label: latest }`, and `store` says so on stderr.

**On an existing skill, `--dir` replaces the file set.** A file missing from the directory is missing from the new version.

Read the first word of the output before going further:

```text theme={null}
stored    incident-triage v4    sre/runbooks (home)
installed /home/you/.claude/skills/incident-triage
on latest — whoever follows `latest` receives it on their next sync
```

Every store ends on that last line. `created` in place of `stored` means a typo made a second skill. It already carries `latest`, so every machine following the project receives it on the next sync: store into the right slug, and archive the stray one from the project's **Skills** page.

If the slug is already taken by a chat prompt, the store fails and names it. A skill's slug can be changed and a chat prompt's cannot, so the skill is what moves aside.

## Who receives it

A machine receives the version its configuration resolves to. A project entry with `label: latest` follows every skill the project has, at its newest version; a skill pinned with `version:` stays there until the pin changes. There is no further step: `latest` moved when you stored, and the next sync on every machine that follows it writes the new version. See [Choosing which skills you receive](https://to11.ai/docs/skills/choosing-skills.md).

## Change one later

Edit the folder and store again. Every store adds an immutable version and moves `latest` to it. `latest` only moves forward, so to take a change back you store the earlier folder again, as a newer version. A machine that must stay on one version pins it with `version:` in its own configuration.

If you edited an installed skill in place, sync leaves the whole of it alone and the row reads `dirty`. Keep your edit with `to11 skill store`, or discard it with `to11 skill sync --force`.

## Next steps

> [card] [What a skill is](https://to11.ai/docs/skills/concepts.md)
>
> What a skill is, what it cannot carry, and what the dashboard shows.

> [card] [CLI commands](https://to11.ai/docs/reference/cli/commands.md)
>
> Every command and flag, and what each one refuses to do.

> [card] [Versions](https://to11.ai/docs/platform/prompts/versions.md)
>
> How versions and the `latest` label work for both kinds of prompt.

> [card] [Receiving skills](https://to11.ai/docs/skills/receiving-skills.md)
>
> Configure a machine so stored skills land where an agent reads them.


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