Skip to main content
Which skills reach a machine, and at which version, is decided by lines in a configuration file — not by commands. Each task below is one edit to skills.yaml, followed by:
sync applies the change and reports what it did; list shows the result, one row per skill. Your own file is ~/.to11/skills.yaml; a repository’s is <repo>/.to11/skills.yaml. If you have neither, run to11 first — see Receiving skills. Every key used here is described in the configuration reference.

Follow the project

A project entry with label: latest installs every skill the project has, at its newest stored version — including one created a minute ago — and each sync brings whatever has been stored since. latest is the only label a skill has, and the one to11 writes when it links a location. Any other value is refused — label: prod fails with `label: prod` is not a label a skill can follow and the hint to follow latest or pin a version with version: <n>.
The tasks below narrow that.

Disable a skill

Name it under the project entry it comes from, with disabled: true:
The next sync removes the files it installed. Any file in that directory you changed or added stays, and the skill reads orphaned until you delete it yourself. A disable in your own file decides your own directories. A repository whose configuration asks for the skill still installs it in the repository. To keep it out of repositories too, write enforced: true beside it:
An enforced disable is off everywhere and nothing overrides it, when both configurations name the same organization and the same project. Both must name the project the same way: by workspace/project, or by id.

Hold a skill at a version

Pin it with version:
The skill stays at v4 while latest moves on. to11 skill list shows pinned 4 (latest: 7) once latest is ahead, and sync leaves it alone. list also prints a line on stderr naming the file that holds it:
Write { label: latest } in place of { version: 4 } to follow latest again. Deleting the line is not the same: in an entry with no project label, the version: is what picks the skill, and without it the skill is no longer received. There is no unpin command: the pin is a line in a file you own. A to11 skill store of a pinned skill moves the pin to the version it stored and says so; it never adds a pin to a skill that follows latest. A pin in your own file is a preference: a repository’s configuration can still decide the version in that repository’s tree. To insist, add enforced: true — see Precedence.

Take one skill without the whole project

Leave label off the project entry. Only the skills named under it are installed, and each says what it follows:
to11 link writes this form when you answer No to Install new skills automatically?, or pass --no-new-skills: skills stored in the project later do not arrive until you add them. to11 skill list names them as available, and to11 link lists them unticked so you can tick one. If the team deletes one of these skills, to11 skill sync keeps the copy you have, warns, and offers to remove it — see sync.

Share a set of skills with a repository

Run to11 inside the repository. In a repository that is not linked yet it links the repository, not your home:
It writes <repo>/.to11/skills.yaml. To answer each question as a flag instead, run to11 link there, such as to11 link --project acme/web --yes. Commit it, and everyone who works in the repository receives those skills in the repository’s own .claude/skills and .agents/skills directories — in addition to their own. A repository’s file never changes a colleague’s own directories, targets or refresh behavior, and it cannot override a skill they have disabled with enforced: true.

Avoid a name you already use

If a published skill would land on a directory name you already have, set a prefix. Every skill from to11 then lands as <prefix>-<slug>:
A directory in a skills folder that to11 did not write is not touched by a normal sync. to11 skill list shows it as not ours, or as blocked when a skill your configuration asks for wants its name — and only to11 skill sync --force replaces a conflict.

Next steps

Configuration

Every key, and exactly how your file and a repository’s combine.

Troubleshooting skills

What each state in to11 skill list means, and how to fix the ones that need you.