Concepts

You can use Airskills without reading any of this. The concepts here are the answers to "wait, why does it do that?" — useful when you start sharing skills with other people, moving them between accounts, or reasoning about why two machines disagree about a skill's contents.

The basics

• Core concepts — skills, skillsets, and organizations. The difference between a personal skill and an organization skill, and how skillsets group them together.

Working with other people

• Share a skill — let someone install one of your skills without transferring ownership.
• Rename a skill — give a skill a different name. Consumers don't notice.
• Transfer a skill — change ownership (user → organization or back). Visible to consumers as "upstream archived."
• Soft delete and restore — airskills rm archives rather than destroys; airskills restore brings it back.

Customising a sourced skill

• Customise a sourced skill — what it means to keep a tweaked variant of someone else's skill alongside their ongoing updates. Optionally suggest changes back to the owner.
• Incorporate updates from the original — the airskills approach to changes from the original. No automatic combining, no line-by-line comparison to pick through. Your agent reads both versions, tells you what changed in plain language, and you decide what to keep.

Cross-skill references

• References between skills — how one skill mentions another via /slug, what airskills tracks, and what it doesn't (no transitive auto-install today — use skillsets for that).

For deeper mechanics — the marker file, commit graph, naming invariants — see under the hood.