Let your whole team build Claude skills
The people who know how your company actually works are rarely the people who can open a pull request or have Admin rights to your Claude Team. SkillHub gives them somewhere to write it down, someone to approve it, and a path straight into your organization's Claude.
Free for 3 published skills. No card required.
What your team writes
Name
Tone of Voice Skill
When Claude should use this
When someone writes copy for our website, newsletter or drafts a new blog post.
Instructions
- Use short sentences.
- Keep the voice active, positive and succinct.
- Be honest and friendly.
What lands in your GitHub repository
plugins/acme-skills/skills/tone-of-voice/SKILL.md
---
description: When someone writes copy for our website, newsletter or drafts a new blog post.
---
1. Use short sentences.
2. Keep the voice active, positive and succinct.
3. Be honest and friendly.
plugins/acme-skills/.claude-plugin/plugin.json
"version": "0.1.3" "0.1.4"
GitHub managed by SkillHub — Claude syncs straight from your repo
Right now, one person is the bottleneck
Org-wide Claude skills reach your team one of two ways. An admin uploads them by hand, one at a time, so every typo fix joins a queue behind that one person. Or they live in a GitHub repo that syncs automatically, which works beautifully for the four people who know what a git commit is.
Neither one works for the marketer who knows exactly how your launch emails should sound, or the support lead who has triaged ten thousand tickets. So the knowledge stays in their heads, or in a doc nobody reads.
How it works
SkillHub provides an interface for your team to write, edit and approve your AI skills. And then automatically syncs them into your Claude organization via a private GitHub repository. It provides a friendly user-interface while retaining your right to own your skills.
- Admin
Point SkillHub at a private GitHub repo
One admin, about ten minutes, once. We create the repository or use one you already have, and set up the structure Claude expects.
- Your team
Anyone writes a skill in plain language
In a document editor, not in YAML. The team can collaborate and freely edit existing shared skills.
- Approver
Someone who knows checks it
Retain control through approval flows. See a before-and-after, open a comment thread, and an approval button. Or no review at all — entirely up to you.
- SkillHub
Skills reach Claude automatically
SkillHub opens the pull request in the GitHub repo, bumps the plugin version and merges it. Nobody has to visit GitHub, and the skills land safely within your Claude Team.
Everything that keeps it safe
An editor for people who don't write Markdown
Formatting toolbar, live preview, autosave. Engineers can flip to the raw SKILL.md whenever they want.
Approval workflow for normal people
Rendered diffs, a required comment when you send something back, and a review queue that empowers your team to edit while keeping things in check.
Four roles, no surprises
Viewer, Editor, Approver, Admin. Nobody approves their own work, whatever their role.
Every version, and a way back
Who changed what, when and why. Roll back to any previous version in one click.
Your repository stays the source of truth
Clean, conventional, hand-editable files and readable commit messages. Edit in GitHub directly and SkillHub picks it up.
An audit log that answers questions
Every publish, approval, role change and policy change, recorded as it happens.
Priced by skills, not seats
- Unlimited members on every plan — we charge for skills, not seats.
- Unlimited marketplaces and GitHub repos on every plan.
- Only published, non-archived skills count. Drafts, archived skills and version history are free.
- Cancel from Stripe whenever you like.
Your content, your repository
Skills are files in a repository you own. Drop us at any time and everything keeps working.
Least-privilege access
A GitHub App scoped to the repositories you pick. No personal access tokens, and no access to anything else.
Nothing published without a check
We validate the complete repository state before writing a single file, and refuse to publish if it wouldn't be valid.
Frequently asked questions
Do I need to know GitHub?
No. One admin connects a repository during setup — after that, nobody writing skills ever sees GitHub. SkillHub opens the pull request, bumps the plugin version and merges it. Engineers who prefer git can keep using it; we pick up their changes.
What if we already have a skills repository?
You can connect your existing GitHub repository to SkillHub. We validate the structure and add anything missing through a pull request you can read first. We only ever touch our own plugin directory and the marketplace catalog — the rest of your repository is left alone.
Where do the skills actually show up in Claude?
In claude.ai on the web, in Claude Desktop, and in Cowork, for everyone in your Claude organization. They do not reach the Claude Code CLI — that is a property of how org-level plugin marketplaces work today, not a SkillHub limitation.
Do I need to be an admin of my Claude organization?
For setup, yes — connecting a marketplace happens in Claude's own settings and needs org-admin access, plus Cowork and Skills enabled. After that, nobody does. The person who connects Claude and the person who connects GitHub can be two different people.
What counts as a skill?
One published, non-archived skill. Drafts don't count, archived skills don't count, and neither does version history.
What happens if we cancel?
Nothing disappears from Claude. Your skills live in your repository, and Claude syncs from that repository — not from us. Cancelling stops new publishes through SkillHub; everything already live stays live.
Can our engineers still use git directly?
Yes. Edit a SKILL.md in GitHub and SkillHub reconciles the change, attributes it to the git author, and shows it in the skill's history. If a skill changed underneath a draft, we warn the editor.
How is our data handled?
Skill content lives in your GitHub repository and is mirrored in our database so we can offer search, diffs and history. We connect through a GitHub App scoped to the repositories you choose, with the narrowest permissions that work. No customer content is used to train anything.
What if a bad skill gets published?
Roll it back in one click — every version is kept. Archiving and rolling back follow the same approval rules as editing.
Someone on your team already knows this. Let them write it down.
Free for 3 published skills. No card required.