Terms of service

You are responsible for what happens under your account. That includes anything done with an API token you create: a token acts as you, and the service cannot tell a token you issued from one somebody took. Revoke a token you no longer trust — that you can do yourself, from your settings. Telling us an account has been taken over needs somewhere to tell it, and no mailbox has been stood up on this domain yet: legal_contact_address_here.

Accounts are for people rather than teams. Use an organization to share access, so that the audit record names whoever acted. The minimum age for holding an account is minimum_account_age_here.

A skill is a set of instructions and files that somebody else’s coding agent will read and act on. That is what makes the first item below the serious one:

An automated scan runs on every publish, and a version that fails it is refused. A registry administrator can override a failing scan, and the override is recorded in the audit log along with the full report. The scan looks for known patterns, so treat it as a filter rather than as a judgement that a skill is safe.

Nobody here reads a skill before it becomes available. A registry can be set to require review, and that review is carried out by that registry’s own administrators rather than by us.

Version numbers are immutable. Publishing the same version twice is refused, because somebody who pinned that number must keep getting the code they pinned. What you can do is narrow:

None of these reaches a copy somebody has already installed. Publishing is the act that makes content durable and distributable, which is the reason to check a package for secrets before you push it rather than after.

You keep ownership of everything you publish. These terms take no ownership of your content, and nothing you publish is used to train a machine learning model.

To run the service we need permission to handle your content, so by publishing you grant a non-exclusive, worldwide, royalty-free licence to host, store, copy, transmit and display it, and to serve it to the people your registry’s visibility allows. For a public registry that is anyone. For a private registry it is the people granted access to it.

That licence lasts as long as we hold the content. It ends for anything we can still reach once you remove it, and it does not end for copies you can no longer reach: a version somebody has installed, or a yanked version an exact pin still resolves.

A skill can declare its own licence in its manifest, and that declaration is the terms you offer the people who install it. The service stores and displays what you declare. It does not check it, interpret it or enforce it.

Installing a skill puts somebody else’s instructions in front of your coding agent, which will act on them. Read what you install, especially before granting it access to a repository or a credential. Content published by other users is theirs, and the service does not vet it, endorse it, or promise it does what it says.

SkillHub is before its 1.0 release. There is no uptime commitment, no service level agreement, and no committed response time for support. Features can change or be withdrawn, and a release can take the service down while it deploys.

There is no status page yet. If the service is down, the honest position is that you will find out by using it, which is a gap rather than a policy.

The service is provided as it is, without warranty of any kind, whether express or implied. Nothing here promises that it will be available, that it will keep your data without loss, or that it is fit for a particular purpose. Keep your own copy of anything you cannot afford to lose.

A limitation of liability belongs here, and writing one is not a job for a draft. The wording, and any cap it sets, are unsettled: limitation_of_liability_here.

You can stop using the service at any time, and you can delete a registry you own without asking anyone. Removing your account is done by hand today, by a person, and there is still no mailbox on this domain to ask at: legal_contact_address_here. The privacy notice sets out what can be removed and what has to stay.

We can suspend or close an account that breaks these terms or puts other users at risk, and we will say why unless saying so would defeat the point. Suspension does not remove versions you published into registries other people own. Those are immutable, and pulling them would break installs their owners did not agree to break.

When this wording changes, the date at the top changes with it. A change that affects what you may publish, or what happens to what you have published, will be announced rather than quietly deployed.

Which law governs these terms, and where a dispute would be heard, follow from where the operating entity is established. That entity is legal_entity_name_here, so both are unsettled: governing_law_here.

Questions about these terms have no address to go to yet, which is itself a clause that has to be written before these terms are put in force: legal_contact_address_here.