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.
Something we haven’t covered? Ask us directly.