Skills and MCP servers, governed
Your team runs Claude Code, Cursor, Codex and Gemini CLI. Each keeps its own folder, in its own layout, with no idea who is allowed to have what. Skill Belt sits behind all four: one catalog, with owners, versions, groups and a log of every fetch.
$99 a month for up to 50 people. Card checkout. No demo call.
$ npm install -g skill-belt$ skill-belt login✓ Signed in to Northwind (northwind)$ skill-belt install Cursor, Codex, Gemini CLI → ~/.agents/skills ✓ 9 installed, 2 updated, 1 removed. Claude Code installs these plugins itself, through /plugin.The gap
Anthropic shipped per-user provisioning, auto-install and SCIM groups in February. It works well and it stops at Claude. If half the team lives in Cursor, or you run through Bedrock or Vertex, none of it is available to you.
The free sync tools go the other way. They will copy a folder into thirty-two clients and cannot tell you who changed it, who is allowed to have it, or which version the contractor is running.
Covered, on a Team or Enterprise plan
No console, no groups
No console, no groups
No console, no groups
Two objects, one policy
Both get the same five things, and that symmetry is the whole trick.
What an agent knows
A markdown file and whatever it references. How your team closes the books. The way you write a migration. The tone your support replies use. Portable across every client that reads SKILL.md.
close-the-month · v7 · owner: Priya · group: Finance
What an agent can do
An MCP server, its configuration and the credentials it needs. The warehouse. The ticket system. The staging deployer that only two people should be able to reach.
warehouse-readonly · v3 · owner: Sam · group: Data
Setup
Nothing here needs a platform team, a Helm chart, or a repository anyone has to be given access to.
STEP 01
No git, no branches, no merge conflicts. Publishing offers patch, minor or major with the exact next number shown — you pick it, you never type it. Saving and publishing are separate buttons, so a draft stays yours until you say otherwise.
Anyone who isn't an owner suggests a change. It arrives as a change request an owner accepts or rejects. Nobody edits a published skill in place.
close-the-month draft · from 1.4.0 ~ owners Priya Raman, Dana Whitfield ~ visibility draft (only you)✓ Saved. Publish when you're ready.STEP 02
Support gets the four skills support actually needs. Data gets the warehouse server with read-only credentials. Contractors get the subset that does not touch production. You assemble the list once.
Groups are manual today and sync from Okta or Keycloak on Enterprise. Either way the entitlement lives in one place.
Finance 12 people → 6 skills, 1 server Support 9 people → 4 skills Data 5 people → 8 skills, 3 servers Contractors 3 people → 2 skills✓ Entitlements updated · effective next fetchSTEP 03
A minute later the skill is inside the agent they already had open. Claude Code reads our marketplace endpoint natively, so it shows up in /plugin. For the other three the CLI writes each skill once, into the folder all three read.
The CLI is open source and MIT licensed. It holds credentials in the OS keychain, and you can read every line of it before you run it.
$ skill-belt install Cursor, Codex → ~/.agents/skills ✓ close-the-month 1.4.0 → close-the-month-review✓ 9 installed. close-the-month draft · from 1.4.0 ~ owners Priya Raman, Dana Whitfield ~ visibility draft (only you)✓ Saved. Publish when you're ready. Finance 12 people → 6 skills, 1 server Support 9 people → 4 skills Data 5 people → 8 skills, 3 servers Contractors 3 people → 2 skills✓ Entitlements updated · effective next fetch$ skill-belt install Cursor, Codex → ~/.agents/skills ✓ close-the-month 1.4.0 → close-the-month-review✓ 9 installed.Sandbox
Not open yetWhich is exactly what a normal free trial hands you. So we are building the opposite: a live admin console loaded with a fictional company. Twelve skills with real owners and version history. Four groups on different entitlements. One change request waiting on you. An audit log with something in it.
It resets every hour and asks you for nothing. It isn't open yet — leave an address and we'll send the link the day it is.
Get the link when it opensDelivery
Every client stores skills somewhere else, and exactly one of them has a marketplace protocol. Keeping up with that is dull work, which is most of why it stays undone.
Anthropic
Native marketplace endpoint
~/.claude/plugins
How it landsAnysphere
CLI writes to disk
~/.agents/skills · .agents/skills
How it landsOpenAI
CLI writes to disk
~/.agents/skills · .agents/skills
How it landsCLI writes to disk
~/.agents/skills · .agents/skills
How it landsPricing
One price, one button, up to 50 people. The only place we ask you to talk to us is Enterprise, where the terms genuinely are negotiated.
$0for 24 hours
Just you, no card
A real org that already happened. You cannot evaluate governance in an empty account, so we do not give you one.
$99per month
Up to 50 people
The whole product, for a team that wants to get people on and actually test it. Bought on a card, in about four minutes.
$2 a head at 50 people.
Buy TeamTalk to us
When IT gets involved
The only place on this site with a contact form instead of a price, and only because these terms are genuinely negotiated.
Scope
Categories like this one collect features until nothing works properly. These four are decided, not still open.
We hand you the config; your agent connects directly. Sitting in the request path is a different product with different uptime obligations, and Obot and MintMCP already do it.
Snyk and Onyx Security do this properly and sell it to your CISO. A publish-time check may show up later. It will never be the pitch.
Skill Belt is your team's private registry. Nobody browses it but you.
LiteLLM and Bifrost are good and free. We are not going to be worse at their job.
FAQ
No. Skills stay plain SKILL.md and MCP config stays plain JSON, and you can export the whole catalog whenever you want. Portability is the argument we're making, so locking you in would rather undercut it.
Those solve copying. Skill Belt solves who-gets-what and who-changed-it. If everyone on your team should have everything and nobody needs to know when it changed, the free tools are the right answer and we'll say so.
They have little reason to serve Cursor, but if they did, the CLI path still works. Claude Code's native marketplace is a convenience for us, not a dependency.
That's most of the point. Authoring is a browser editor with a save button and a publish button, and diffs read as prose, side by side. Nobody opens a pull request to change a paragraph.
Not publicly. We're building with a handful of design partners, and the sandbox opens before general availability. If you'd like to be one of them, the contact form is the fastest way in.
Questions
Pricing, the sandbox, whether it works with an agent we haven't listed, or why we refuse to build the thing you actually want. A person reads these and replies, usually the same day.