Claude skills, under management
Governance for the skills your AI reads.
The review layer for your company’s Claude skills. The person who owns the knowledge proposes the change from inside Claude, an approver signs off, and it publishes. Nobody learned Git.
Set up one company at a time
There is no self-signup. We create your workspace and invite your first admin, who connects your repository and brings in the rest of the company.
A proposal waiting for review. Synthetic data.
Distribution is solved. Management is not.
Connect a GitHub repository to your Claude organization and everyone in the company has your skills within about thirty minutes. That part works. What Anthropic left to you is everything after: who may change a skill, who signs off, what happened last Tuesday, and how to undo it.
In practice that locks out exactly the people who should be writing these files. The sales lead who knows what a good discovery call sounds like has no GitHub account and shouldn’t need one. So one engineer becomes the bottleneck for knowledge they don’t own, and the skills go stale.
How a change happens
Someone asks Claude for a change
A sales lead says the discovery-call skill should ask about budget. Claude reads the current skill through the Skillhouse connector, works out the wording with them, and submits it. They never see GitHub.
Claude checks it first
Skillhouse lints the files and, by default, has Claude review the draft, producing a summary a non-engineer can read and risk flags the requester can act on before anyone else is involved.
An approver decides, and it publishes
The department's approver sees the summary, the flags, and the diff. On approval Skillhouse commits to your repository through a GitHub App, or opens a pull request if your IT team wants that gate. Claude picks it up on its next sync.
What you get
Proposals happen inside Claude
Claude fetches the live skill through Skillhouse, works the change out with the requester in conversation, and submits it. No repo access, no branches, no ticket sitting in someone else's queue.
Checked before a human sees it
Every draft is linted, and unless your workspace turns it off, reviewed by Claude first: a plain-English summary and risk flags, such as a skill that would send client data to an outside system. The requester fixes problems before an approver spends time on them.
Approval that matches your org
Proposals route to the approvers for that department. They can approve and publish, request changes with a note, edit before approving, or reject. A warning fires if the skill moved underneath the proposal.
A real audit trail
Every change is a signed commit naming the approver. Every version is kept, any skill can be rolled back, and the log records who proposed, who approved, and when it went live.
What standing it up takes
About thirty minutes of an admin’s time, with a guide in the app that tracks what is done and what is left. You need a GitHub repository for your plugins; if you already publish skills to Claude, that is the one you have.
Connect your plugin repository
Install the Skillhouse GitHub App on the repo that holds your Claude plugins. It asks for contents and pull requests, plus read-only metadata, and the guide has you scope the install to that one repository. Skills already there import themselves.
Point claude.ai at the repo
An admin for your claude.ai organization adds the marketplace once, and everyone in the company has the skills. This step and the GitHub one often belong to a colleague, so each has a hand-off email built into the guide.
Add your departments and people
Build the department tree, invite people by email, and give them a role. Roles inherit down the tree. Each person adds the Skillhouse connector to Claude once, and they can propose from then on.
Skillhouse runs as a hosted workspace for your company, with your data kept separate from every other workspace. People sign in with a work email link, Google, or Microsoft.
Interested in a workspace?
Tell us about your team and how your skills live today. We will show you Skillhouse against your own setup and stand up a workspace if it fits.
Get in touch