Writing skills is easy. Getting them everywhere isn't.

Back up, publish, and sync your skills across your team. Standard format, no lock-in. Start solo in 10 seconds.

Start with simple storage and push. Expand to team distribution when you're ready. Works with Claude Code, Cursor, Copilot, Windsurf, Cline, ChatGPT, and more. Open source CLI (MIT).

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

CLI installs to every agent on your machine

terminal

Start with the easy thing

Use airskills as the easiest place to keep skills and push them where you need them. No big migration. No proprietary format.

npx

npx airskills add chrismdp/retro

npm

npm install -g airskills

Terminal

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

Windows

irm https://airskills.ai/install.ps1 | iex

$ airskills sync

✓ Found Cursor ~/.cursor/skills/

✓ Found Claude Code ~/.claude/skills/

✓ Found Copilot ~/.copilot/skills/

Pushing your skills to every detected agent...

✓ Synced

Sync writes your SKILL.md files to each tool's skill directory. The format is the same everywhere because all AI coding tools read plain markdown instructions.

Or skip install with MCP

Any tool that supports MCP can load skills from airskills without installing anything. No CLI, no files on disk, no setup. Just point your tool at one URL.

Add this as an MCP server in your tool

https://airskills.ai/mcp

Works with Claude Code, Cursor, Copilot, Windsurf, Cline, ChatGPT, and any tool that supports remote MCP servers. Log in with airskills login to access private and team skills. Without login, only public skills are visible.

The MCP endpoint is read-only and enforces the same row-level security as the API. Security details

No lock-in

The standard objection is sensible: storing your skills somewhere new sounds like lock-in, but airskills is a convenience layer on top of normal files.

• Uses plain SKILL.md files that most AI tools already read
• Writes to the skill directories your tools already use
• Open-source CLI you can inspect and run yourself
• Portable files: export, copy, or stop anytime
• CLI works offline with no account

Use airskills because it's easier to store and push skills, not because it traps you in a new format. Start with one skill on one machine. Expand to cross-machine sync and team rollout only if it helps.

The CLI sends your skill files when you push, not your code or git history. Telemetry is lightweight and can be disabled with AIRSKILLS_NO_TELEMETRY=1. Binaries are checksummed and signed. Source on GitHub.

Read our full security details →

Stop being your team's AI janitor

You wrote the original skills. You update them when things break. New joiners ask you where to find them, and you are one holiday away from the whole setup falling apart. For teams, the core problem is distribution.

What happens today

Skills are shared in Slack, docs, or repos.
Some people install them. Others never do.
Local edits create private variants no one else sees.
No visibility into who has what version.
Updating the team standard means manual chasing.

With airskills

One place to store approved team skills.
Push to every supported tool and machine.
Reduce drift with shared versions and history.
Make rollout simpler for new joiners and existing teams.
Keep the underlying files portable and inspectable.

Install in 10 seconds Apply for trial

Push skills anywhere. Your files, your format. github.com/chrismdp/airskills