OpenAI
Codex reads .agents/skills. We decide what goes in it.
Codex CLI has no notion of a team catalog. Skills are files, files get copied around, and six weeks later nobody knows which version anyone is running.
.agents/skills is the folder Codex shares with Cursor and Gemini CLI, so it is the one target for all three. The CLI writes the entitled set there — each skill in its own folder, named for the plugin it came from — and removes anything that is no longer entitled on the next install.
MCP servers reach Claude Code today. For Codex, the CLI installs the skills and tells you plainly what it skipped, rather than writing half a server config.
For teams running Codex alongside a Claude or Cursor population, the catalog and the groups are the same ones. The delivery mechanism differs; the policy does not.
$ npm install -g skill-belt$ skill-belt install --client codex ✓ incident 3.2.0 → incident-runbook Claude Code only, not installed here: MCP servers✓ 9 skills in ~/.agents/skills- Delivery
- CLI writes to disk
- User path
- ~/.agents/skills
- Project path
- .agents/skills
- Credentials
- OS keychain
Known limits
What Codex CLI does not give us.
Stated up front, because you will find these out on day two anyway.
- No marketplace protocol and no admin surface of any kind, so everything runs through the CLI.
- MCP servers and hooks are Claude Code only, for now.
FAQ
Codex CLI, specifically.
Does Skill Belt work with the Codex IDE extension too?
Wherever the extension reads the same on-disk paths, yes. The CLI writes files; it does not hook into any particular front end.
Where does my Skill Belt credential end up?
In the operating system keychain. It is never written into a file in your repository, and never printed.
Also delivers to
The price is on the page. That is the whole idea.
$99 a month for up to 50 people, cancelled from the billing page. If you've got a question first, ask it — a person answers.