Claude just made governance and distribution a first-class path for agent skills.
Orgs used to shoehorn governance and distribution through Slack, Drive, and GitHub. A native org library with review changes that for teams that need to move fast without losing the plot.
When a team starts getting real value from AI agents, the next problem shows up fast. Someone builds a sharp skill for proposals, security checks, or client follow-up. It works. Then it stays on their machine. Everyone else keeps reinventing a weaker copy.
Shoehorned governance was the stopgap
Until recently, orgs that cared about quality had to shoehorn solutions for governance and distribution. Slack threads. Drive folders. A GitHub repo and a prayer that people used the latest version. Those paths can work. They were never designed for sharing the best version of an agent skill across people and teams, with a clear gate before it becomes the company way.
What Claude just made native
Claude now lets Team and Enterprise orgs publish skills and plugins into an organization library. Owners set publishing policy under Organization settings → Skills → Policy → Publishing: Requires review, Open, or Off. With Requires review, a member submits, an owner approves or requests changes, and every later version goes through the same gate. Open publishes to the library without that review step. Off hides Publish to org for members; owners can still add skills and plugins directly.
That is a governed path from one person's best practice into a shared library teammates can find and install, without inventing a side process in Slack, Drive, or GitHub.
Why this accelerates SMBs, not only enterprises
A 10 to 100 person company rarely has a platform team to invent internal marketplaces. What it does have is a few people who build excellent automations and a lot of people who need them. Native review plus an org library means the company can treat agent workflows like product: a home, a checkpoint, and a path to the people who need them.
Open if you want speed. Requires review when the skill touches customers, money, or security. Either way, tribal knowledge stops winning by default.
Use the console below. Flip the publishing policy and see how the path from a personal skill to the org library changes.
Author submits. Owner approves or requests changes. Then the library.
Governance is the policy. Distribution is the library. Together they let the best skill become the company skill.
Ready to transform your business with governed automations and agents that actually travel across the team?
Foundry helps enable AI transformation: shared memory, agents that run on it, and oversight as infrastructure. Contact us when you want the best workflows to travel across the team, not sit on one machine.
Contact us →