One copy, every agent

Skillet keeps one copy of each skill in ~/.skillet and writes it into every runtime you connect, each in the format that runtime expects. Edit the copy once and every runtime has it on the next sync.

Install SkilletFree. Mac, Windows, or the CLI.

Where skills live

~/.skilletholds the clean copy. It is the only one you edit. Everything under a runtime’s own skills folder is written from it and can be regenerated.

Runtime	How it gets the skill
Claude Code, Cursor, Codex	Written to that runtime’s skills folder on sync
Windsurf, Devin, Hermes, OpenClaw, OpenCode	Same, in each one’s own format
ChatGPT, Claude.ai	No skills folder, so they read the same store over MCP

Adding a runtime does not mean porting what you own. The canonical copy has not changed, so the new adapter writes the same skills into one more place. Every supported runtime

How updates land

Nothing on your machine changes until you approve it. Editing your own skill is the exception: your own republish flows to your machines without asking, because approval exists to gate other people’s changes.

1
The author publishes a new version
The old version stays on your machine.
2
The update queues at /updates
Each row shows the skill, the version it moves to, and a diff of what changed.
3
You take it or leave it
Update applies it, Skip declines it, Update all clears the batch. Approve some and leave the rest pending.

Auto-apply:: Off by default. Turn on Auto-update subscribed skillsunder Settings > Account and signed, scanned updates apply on next sync instead of queueing
Where approval happens:: The web, at /updates, or the same queue in the app. The website cannot write to disk, so the app or the CLI does the sync

Skills you have edited

Hand-edit a synced skill and sync keeps your edit. That skill gets its own section on the updates page and is held out of Update all, so it moves only when you decide.

Choice	What happens
Upgrade	Their version applies, your edit is backed up first and stays recoverable
Leave it	Your edit stays exactly as it is and their future versions keep queueing

Good to know

Your edited content never leaves the machine. Skillet records only that a skill was edited on a device: which skill, which device, and which version you edited from.

Recovery

Atomic:: An update applies completely or not at all. A half-written skills folder is not a state you can land in
Backed up:: Your previous version is saved before anything is written, so a bad update is recoverable
Immutable:: A published version never changes after the fact, so the version you approved is the version you keep
Never deleted:: Skillet does not remove your skills. If a sync fails you keep what you had

Kits

A kit is a named set of skills. Two things describe any kit: who owns it, and who can see it.

Kit	Who sees it	Use it for
Personal	Just you, unless you publish	Your own skills
Team	Members, and every tool they connect	Runbooks that must not drift between people

A team kit puts every member and every CI runner on the same approved version. Incoming changes arrive as diffs the same way. A skill can sit in more than one kit without leaving yours.

Limits

The website cannot write to your disk. Approving an update in the browser records the decision. The app or the CLI applies it on the next sync.

Cloud runtimes do not auto-sync. ChatGPT and Claude.ai have no local skills folder, so they read the store over MCP or take a downloadable bundle you upload.

Updates are scanned, not certified. A scan flags what it can and links the report next to the diff. A person decides.

Next steps