Skip to main content
You need the to11 binary on your PATH and an API key, which you create in the dashboard under Settings → API keys. Nothing else — skills arrive as files, so there is no runtime to install and no agent setting to edit by hand.

​
Install the CLI

​
Install with asdf

Requires asdf 0.16 or newer.

​
Manual installation

Get the latest release from the to11-cli repository and install the to11 binary manually.

​
Configure this machine

init resolves your identity and project, lists the project’s real environments so a label is chosen rather than typed, writes your configuration, creates your agent’s skill directories, offers a refresh hook, and runs a first sync. It asks for the API key at a hidden prompt. Every other question has a default, so the rest is answerable with return presses:
The refresh hook is an offer. Decline it and nothing is wrong — the skills you have stay where they are, and they update when you run to11 skill sync or whatever else you schedule to. If a published skill would land on a directory name you already use, answer prefix with a name — acme delivers acme-<slug> instead of <slug> — and every delivery moves out of the way at once.

​
Configure a repository

To decide which skills apply to work in a repository, run init inside it and choose the repo location:
That writes <repo>/.to11/skills.yaml, which is committed. Your own configuration still applies — both are in effect at once, each writing into its own directories — so a repository adds skills to a colleague’s machine without taking over how their agent behaves.

​
Configure without a terminal

For CI, a container, or a provisioning script, supply every flag and init asks nothing:
Without a terminal there is no prompt, so the key comes from TO11_API_KEY in the environment. Inject it from your CI provider’s secret store rather than writing it into the command or the script — a value on the command line reaches your shell history and the environment of everything the script starts. There is no flag that takes the key, so no invocation can carry it by accident.

​
Check what you received

One row per skill, with its version, its state, the target it went to and where it came from. A skill your configuration names but that did not arrive is a row too, and its state is the reason. If something needs putting right, to11 skill sync runs an explicit sync and reports what changed, what it left alone, and what it could not place.

​
Next steps

CLI overview

What the CLI puts where, how refresh works, and what it never does.

Configuration

The file that decides what you receive — including how to turn a skill off.

Creating skills

Writing a skill, and releasing one to the people who follow a label.

Errors & exit codes

What a failure looks like, and what keeps working when one happens.