Get started
StandardsSkillRightsSkillsLicensing

How to license an AI agent skill

To license an AI agent skill, put a licence identifier in your SKILL.md frontmatter, keep the text beside it and add one README line. Here is how, with the open SkillRights licences and one command, plus what a licence can and cannot do.

Adam Cowles18 November 20266 min read
A glass document card with a glowing cyan header strip, orbited by two bright blue keys and one dimmed violet key behind a fine lattice, on near-black

To license an AI agent skill, put a licence identifier in the license field of the skill's SKILL.md frontmatter, keep the licence text in a LICENSES/ folder beside it, and add a one-line notice to the README. SkillRights, an open licence family for agent skills, gives you three ready-made licences and a free command-line tool that does all three steps in one command.

This is the practical version. The argument for why skills need their own terms is in Your expertise is not training data. Proving you held a skill first is covered in You wrote the skill. Can you prove it?. This post is about getting a licence onto the file.

Why not just put MIT on a skill?

A skill is executable expertise: procedures, judgement and methodology written down so a machine can act on them. Publishing one so agents can use it should not silently grant permission to absorb it into a model. Current licences blur those two things together.

SkillRights separates four rights: execute, train, redistribute and commercial use. Train is one deliberately broad right covering training, fine-tuning, distillation and deriving synthetic training data. There is also a clear boundary for retrieval: using a skill in a RAG pipeline at inference time counts as execution, while building an embedding or corpus to improve a model counts as training.

Which licence should an AI agent skill use?

There are three named licences, all version 1.0. Pick the one that matches what you want to allow.

LicenceExecuteTrainRedistribute
LicenseRef-SkillRights-Open-1.0YesYesYes, with attribution
LicenseRef-SkillRights-NoTrain-1.0YesReservedYes, with attribution; modified copies stay under this licence
LicenseRef-SkillRights-Reserved-1.0Authorised recipients, internal business use onlyReservedReserved

Commercial use: yes under Open and NoTrain, by agreement under Reserved. Full texts at skillrights.org.

Choose Open if you are happy for anyone to run it, share it and learn from it. Choose NoTrain if you want agents and people to use and share the skill but not train models on it. Choose Reserved for internal or client skills that should only run for people you have authorised.

Where does the licence go in a SKILL.md file?

Skill files such as Anthropic's SKILL.md format, the one Claude skills use, already define an optional license frontmatter field. SkillRights uses that field unchanged, so a Claude skill license is one line:

---
name: pr-reviewer
description: Review a pull request the way our senior engineers do.
license: LicenseRef-SkillRights-NoTrain-1.0
---

That line is about 20 tokens, read only when the skill is invoked. For human readers, crawlers and corpus filters, the specification also asks for one plain line near the top of the README:

SkillRights-NoTrain-1.0: AI execution permitted. Model training rights reserved. https://skillrights.org/notrain/1.0

Following the SPDX LicenseRef- convention, the full licence text sits in a LICENSES/ folder in the same repository.

How do I license a skill in one command?

You can write those three pieces by hand, or let the skillrights CLI do it. It needs Node.js 18 or later, has no dependencies and no telemetry, and asks for no account. Here it is on a small skill folder containing a SKILL.md and a README:

npx skillrights init ./pr-reviewer --license notrain --author "Acme Data"

The tool reported exactly what it changed:

- Wrote LICENSES/LicenseRef-SkillRights-NoTrain-1.0.txt.
- Updated SKILL.md frontmatter (license: LicenseRef-SkillRights-NoTrain-1.0, author: Acme Data).
- Appended the SkillRights header line to README.md.

Every other frontmatter line is left alone, and running it twice changes nothing the second time.

Then confirm the declaration hangs together:

skillrights check ./pr-reviewer
# PASS
# - SkillRights declaration OK: LicenseRef-SkillRights-NoTrain-1.0.

check exits 1 and names the problem if the identifier is unknown, the licence file is missing, or the two disagree, so it can gate CI. There is also a ready GitHub Action that runs it on every push.

skillrights explain notrain prints a plain-English summary of what the licence allows. If you would rather not use a terminal, the generator on skillrights.org builds the same declaration in the browser, with no account. It also offers example robots.txt and TDMRep signals for skills published on the web, which the CLI does not generate.

What can a skill licence actually do?

Honesty matters more here than anywhere, so this is what the SkillRights specification itself says. A declaration is a dated statement of your terms and of non-consent. It is not a technical shield against scraping, and it does not stop anyone copying a file.

  • EU: it supports a text-and-data-mining rights reservation under Article 4(3) of the DSM Directive; whether a signal qualifies depends on the facts and national law.
  • UK: that Directive does not apply, but UK exceptions may.
  • US: it does not by itself bind someone who never agreed to it, or remove fair use.
  • Marketplaces and contracts: accepted terms are where enforcement is strongest today.

Two more limits worth knowing. The 1.0 texts were produced through adversarial review by two independent AI reviewers; they are not advice from qualified counsel, and professional review is still planned. And a licence states terms without proving who wrote the skill. For dated, signed evidence, see skillrights sign and register, covered in the proof walkthrough.

Frequently asked questions

Do I need Quox to use SkillRights?

No. Quox initiated SkillRights and maintains it, but the licences, the specification and the CLI are free and need no Quox account or software. Quox's own take on rights-aware skills is on the QuoxSkills page.

Does it work for skills that are not Claude skills?

The declaration uses the license frontmatter field that skill formats already have. Anthropic's SKILL.md is the format the CLI edits directly.

Can I change my skill's licence later?

Re-run init with the new --license. It updates the frontmatter and writes the new licence file, but leaves the old README line and old licence file in place, so remove those by hand. The identifiers never change meaning: SkillRights-NoTrain-1.0 will always mean the 1.0 text.

Is the CLI open source?

Yes. The CLI and the GitHub Action are MIT licensed. The licence texts may be copied verbatim to apply them to any work.