About Skillet
Skillet is a registry for agent skills. A skill is a SKILL.md file, plus any scripts, references, and assets it needs, that an AI agent loads to gain a capability: review a diff the way your team reviews diffs, draft a changelog in your house voice, triage an incident against your runbook. Publish it once here and it reaches every agent runtime you use.
What it does
Agent runtimes each keep skills in their own folder, in their own format. Skillet holds one canonical copy per machine and syncs it outward, so Claude Code, Codex CLI, Cursor, Claude Desktop, and the rest all read the same version of the same skill. Clients that have no skills folder read the same store over MCP.
The other half is discovery. Anyone can browse what other people publish, subscribe to a person’s kit, and pull their skills into their own agents. Good practice usually exists somewhere already; the hard part is finding it and keeping it current.
How updates work
Nothing changes on your machines without your say-so. When an author publishes a new version of a skill you use, it waits in Updates until you approve that specific version. Approval is per version, not a standing grant, and the web is the only place it happens.
Safety
Skills are instructions an agent will act on, so every published version is scanned before it is served, and quarantined content is never downloadable. The scanner reference documents what it looks for and what it cannot catch. Verdicts are public: you can check any version before you run it.
Who runs it
Skillet is an independent open-source project, not a company. The code is on GitHub under Apache-2.0: the web app, the registry, the CLI, and every runtime adapter. You can read exactly what it does with your skills, or run your own instance.
For agents
The public catalog is a JSON API that needs no credentials to read, described at /openapi.json. Every page here also serves clean Markdown at the same URL when you ask for it with Accept: text/markdown. Start at /llms.txt or the API guide.
Reach us
Questions, bug reports, and takedown requests all have a route on the contact page.