Airskills documentation

Sync, version, and share AI coding skills across every agent, every machine, and your team

Airskills is one home for your AI agents' skills — the SKILL.md files that teach Claude, Cursor, Copilot, and others how to do things your way. Write a skill once, push it, and it flows to every agent on every machine you use, plus every teammate you share it with.

Quick start

curl -fsSL https://airskills.ai/install.sh | bash
airskills sync

The first airskills sync logs you in, scans your machine for installed AI agents, and pushes your local skills up to your account. From then on, every other machine you run airskills sync on stays in step.

The three concepts you need

Skills — one SKILL.md file per thing you want the agent to know how to do.
Skillsets — curated groups of skills you install in different places, or that your team curates and assigns to you on your behalf.
Organizations — a shared account for a team. Admins edit the team's skills; other members suggest changes back, and admins decide what to take. Members can also keep their own local tweaks while still receiving updates from the team. That last bit is unusual — read on.

See Core concepts for the full story.

And one idea that's not what you expect: incorporation

Most version-control tools make you pick between "take the upstream version" and "keep mine, lose the updates". Airskills does neither. Skills are not code; we don't try to merge them and we don't make you read a diff. When the original changes, your AI agent reads the new version and explains in plain language what's different — you decide, in one sentence, what to bring in.

What this gets you:

As someone using a skill: keep your own slightly-modified copy of a teammate's or stranger's skill and still receive their improvements. No "fork or fall behind" trade-off.
As someone maintaining a skill: you don't have to read endless diffs from people who tweaked your skill. Suggestions arrive as plain-text requests; you decide whether to take them.

Common workflows

Rename a skill — airskills mv to give a skill a new name. Consumers don't notice.
Share a skill — let someone install one of your skills without transferring ownership.
Transfer a skill — hand your skill to an organization, or pull an organization skill back.
Archive a skill — airskills rm archives rather than deletes, and you can restore it later.

Reference

CLI reference — every command, every flag.
HTTP API reference — the REST endpoints the CLI talks to. Useful if you're wiring Airskills into your CI, your agent, or your own tooling.

Customisation

Customise a sourced skill — tweak someone else's skill without losing the connection to their updates.
Incorporate updates from the original — have your agent read the new version and bring across only the parts you want. The CLI doesn't try to combine versions for you; you stay in charge.

Under the hood

The mental model below the surface — most of the time you don't need these, but they're here when something looks odd or you're extending the system:

Was this page helpful?