Claude skill approval: the missing workflow.

What Anthropic's documentation actually says

Claude Team and Enterprise plans now ship real distribution: admins can provision skills centrally, members can share skills with each other or publish them to an organization directory, and plugin marketplaces can sync automatically from a private GitHub repository. Distribution, in other words, is solved.

Approval is not, and Anthropic says so plainly. Per the official guidance on provisioning and managing skills: when organization sharing is enabled, any authorized member can publish a skill to the whole organization, and no review step exists. The sharing audit records that a share happened, not what was shared. There is no admin view to browse the content members have published to each other. And the workaround the documentation itself suggests is to disable organization sharing and ask members to submit their skills manually to a designated owner.

Read that twice: the recommended fix for unreviewed sharing is to turn sharing off.

Why this bites at around fifty people

With eight people, open sharing is fine. Everyone knows who wrote what, and a bad skill gets caught over coffee. The problem compounds with scale:

A skill that quotes last quarter's pricing keeps answering under your brand. A method one rep half-tested becomes forty reps' default. Two teams publish three variants of the same brief and nobody knows which one the company stands behind. When the author leaves, their skills stay published and unowned. None of this is malicious; it is what happens when publishing is one click and reviewing is nobody's job.

The manual queue, and why it quietly breaks

So companies do the documented thing: they disable organization sharing and appoint an owner. Employees send skills over chat. The owner reads them between meetings, edits by hand, uploads what passes. This is an approval process run on goodwill, and it fails in predictable ways: the queue lives in someone's DMs, there is no record of what was approved or why, the version that ships is whatever file was attached last, and the owner becomes the bottleneck for every team's methods, including the ones they know nothing about. Sales methods reviewed by an IT admin is how good methods die and bad ones pass.

What a real skill approval binds to

An approval worth the name is not a thumbs-up in a channel. It binds five things together:

The right reviewer. The person accountable for the process: a renewal method goes to the Head of Customer Success, a close checklist to Finance. Domain experts, not IT.

The exact version. The approval applies to the precise content reviewed. If the skill changes afterwards, the approval no longer applies, and the reviewer decides again on the new version.

The evidence. Checks run against that same content: does it trigger when it should, cite what it uses, respect its constraints? The reviewer decides with the results in front of them.

The scope. Approved for whom? A skill for the Sales team ships to the Sales team, not to everyone with a login.

The record. Who approved what, in which version, when. Kept as history, so "which one is official?" always has an answer.

And one absence matters as much as the five presences: no bulk approval. Fifty skills approved in one click is zero skills reviewed.

The approval path, without leaving Claude

The reason approval gets skipped is friction: if reviewing means adopting another tool, nobody reviews. The path that works keeps everyone where they already work. An employee turns a proven method into a proposal from Claude, previewing exactly what gets sent. Their lead gets a ping, opens the review in Claude, sees the exact version, what changed, and the check results, then requests changes or approves. Only then does the skill ship, to the chosen team, through the distribution Claude already provides. The queue is gone, the record exists, and nobody adopted anything.

How knacks does it

knacks is the approval layer for company skills: it adds exactly the step Anthropic documents as missing, in front of the distribution Claude already does well. Employees propose from Claude, the right expert approves the exact version with the evidence attached, and knacks publishes only what was approved, to one team or the whole company. Every decision is recorded, every published version lives as plain files in a GitHub repository your company owns, and nothing is read from anyone's conversations. See how an engagement starts: one team, one repeated task, the first approved skill live in the first week.