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 withlabel: 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>.
Disable a skill
Name it under the project entry it comes from, withdisabled: true:
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:
workspace/project, or by id.
Hold a skill at a version
Pin it withversion:
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:
{ 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
Leavelabel 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
Runto11 inside the repository. In a repository that is not linked yet it links the repository, not your home:
<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 aprefix. Every skill from to11 then lands as <prefix>-<slug>:
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.