> ## 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.

# Skills quickstart

> Receive your team's skills, and publish a skill of your own that everyone who follows the project receives.

In this tutorial you will set up the to11 CLI, receive the skills a project already has, write a small skill of your own, and store it. By the end, Claude Code reads skills that to11 keeps current, and you have stored a version other people receive.

You need a to11 account in your company's organization, a [project](https://to11.ai/docs/platform/projects.md) you can create prompts in, and Claude Code installed. On macOS, you also need [Homebrew](https://brew.sh).

## Install the CLI

```bash macOS theme={null}
brew install to11ai/tap/to11
```

```bash Ubuntu & Debian theme={null}
sudo apt-get update
sudo apt-get install -y curl gnupg
curl -fsSL https://apt.fury.io/to11/gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/to11-keyring.gpg
sudo chmod go+r /usr/share/keyrings/to11-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/to11-keyring.gpg] https://apt.fury.io/to11/ * *" | sudo tee /etc/apt/sources.list.d/to11.list
sudo apt update
sudo apt install to11
```

```bash Fedora & RHEL theme={null}
sudo rpm --import https://yum.fury.io/to11/gpg.key
sudo rpm --import https://raw.githubusercontent.com/to11ai/to11-cli/main/rpm-signing-key.asc
sudo tee /etc/yum.repos.d/to11.repo <<EOF
[to11]
name=to11 Repository
baseurl=https://yum.fury.io/to11/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://yum.fury.io/to11/gpg.key
EOF

sudo dnf install to11
```

```bash theme={null}
to11 version
```

This tutorial needs version `0.36.0` or later. If `to11 version` prints an older one, upgrade with the same tool you installed it with: `brew upgrade to11ai/tap/to11`, `sudo apt update && sudo apt install --only-upgrade to11`, or `sudo dnf upgrade to11`.

## Set up this machine

Run this from your home directory, not inside a git repository:

```bash theme={null}
cd ~
to11
```

`to11` links your home to a project and fetches its skills, asking one question at a time in the terminal:

1. At `Press Enter to continue in your browser, or Ctrl-C to cancel.`, press Enter and sign in in the browser.
2. At `Which project?`, choose the project you will publish to. If it asks `Which organization?` first, choose your company's.
3. At `All skills are installed, including ones published later:`, press Enter for **OK**. The names under it are the skills the project publishes on `latest`. If it says `No skills published yet.` instead, press Enter at `Install new skills automatically?` to keep the default, Yes, so the skill you store later in this tutorial arrives.
4. Check that `Skills are installed for:` names Claude Code with `~/.claude/skills`, and press Enter for **OK**. If it does not, move to **Customize** with the arrow keys, press Enter, and select **Claude Code**.
5. Answer `y` to `Install the to11 plugin for Claude Code?` — `for Claude Code and Codex?` when Codex is installed too. The plugin keeps your skills current while Claude Code is open.
6. At `Sync your Claude Code sessions to to11 automatically?`, press Enter to keep it off.

`✓ Linked skills from <project> @ latest` names the project, `Saved to` the file it wrote, `~/.to11/skills.yaml`, and the rows after it are every skill the project has, fetched into place — under a header naming the folders and the agents that read them, one row per skill with its version. Run `to11 ui` whenever you want to see everything that is set up at once.

## See what you received

```bash theme={null}
to11 skill list
```

Each row is one skill, under the project it comes from. A project that already has skills shows them as `unchanged` — installed and current. A project with no skills yet shows no rows from to11; that is fine, the next step adds one.

## Write a skill

A skill is a folder whose entry document is `SKILL.md`. Create one:

```bash theme={null}
mkdir -p ~/skills-tutorial/commit-style
cat > ~/skills-tutorial/commit-style/SKILL.md <<'EOF'
---
name: commit-style
description: Write commit messages in this team's Conventional Commits style.
---

When you write a commit message:

- Use a Conventional Commits type and a scope: `fix(api): …`.
- Keep the subject under 72 characters, in the imperative mood.
- Put the ticket ID at the end of the subject in brackets: `[TO11-123]`.
EOF
```

The `description` matters: an agent decides whether a skill is relevant by reading it.

## Store it

```bash theme={null}
to11 skill store commit-style --dir ~/skills-tutorial/commit-style
```

```text theme={null}
created   commit-style v1    acme/platform (home)
installed /home/you/.claude/skills/commit-style
on latest — whoever follows `latest` receives it on their next sync
```

`created` tells you this is a new skill rather than a new version of an existing one. If you also kept Codex selected, a second `installed` line names `~/.agents/skills`. The skill is on your machine, and your agent can use it. The last line is the point: storing a version moves the skill's one label, `latest`, so everyone who follows the project receives `commit-style` on their next sync — automatically while their agent is open, or on their next `to11 skill sync`.

Run `to11 skill list` again: the row for `commit-style` reads `latest · 1`. Your configuration follows `latest`, which is the version you just stored, so the next version anyone stores reaches you too.

## Try it

Open Claude Code and ask it to write a commit message for a change. It picks up `commit-style` from its skills directory.

## What you did

You configured a machine to receive a project's skills, and stored a skill that everyone following the project now receives. Every later change works the same way: edit the folder, `store`, try it.

## Next steps

> [card] [Sessions](https://to11.ai/docs/sessions/overview.md)
>
> Upload your Claude Code sessions and read them in the dashboard.

> [card] [Publishing skills](https://to11.ai/docs/skills/publishing-skills.md)
>
> Descriptions, reference files, and the other details of storing a version.

> [card] [Choosing which skills you receive](https://to11.ai/docs/skills/choosing-skills.md)
>
> Disable a skill, hold a version, or share a set with a repository.

> [card] [What a skill is](https://to11.ai/docs/skills/concepts.md)
>
> The folder format, its limits, and what a skill cannot carry.


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