How to share Claude skills on GitHub, and who it reaches

Three ways compared

From the Claude Code docs and Claude Help Center, read 5 November 2026.

A worked example: one repo, two kinds of teammate

Illustration: a made-up business. A 12-person software agency keeps its skills in a private repository, acme-studio/skills: a code-review checklist, a release-notes writer and a client status report. Engineers and project managers both need them.

• Engineers add the repository as a plugin marketplace once. The code-review skill runs in Claude Code as /studio:code-review, and Claude picks the release-notes skill when they ask for release notes. When the lead edits a skill, it reaches them through plugin updates.
• Project managers use Claude in the browser. For them the repository is a folder of files. The first month, two of the four were using an old status-report skill because they'd never re-uploaded it.

The fix was a second route for the project managers, not more reminders. Their status-report skill now comes from one place their Claude connects to, and the engineers keep GitHub.

Set up a skills marketplace on GitHub

1. Make a repository with a plugins/ folder. Each plugin is a folder whose skills sit in skills/<skill-name>/SKILL.md.
2. Add .claude-plugin/marketplace.json with a name, an owner and a plugins list; each entry has a name and a source such as ./plugins/studio.
3. Validate it: claude plugin validate .
4. Push it to GitHub; a private repository works for people with access.
5. Teammates run claude plugin marketplace add acme-studio/skills, then claude plugin install studio@<marketplace-name>.

Teammates who don't use GitHub

Most teams have them: managers, sales, support, the freelancer. Three ways to reach them without downloads:

• Claude Team or Enterprise: an owner deploys the skills to the organization. Only reaches people in your Claude organization.
• Their own claude.ai account: skills they enable there also sync into Claude Code, so one upload serves both apps on their machine.
• A shared skill library over MCP: one copy, connected from Claude on any plan, ChatGPT Pro, Business or Enterprise, and coding agents. AI Skill Pod is one, with Free for up to 3 members and 10 skills.

Sending teammates the link? How to install Claude skills from GitHub is their side: claude.ai, Claude Code and Codex, step by step. Writing the skills themselves in Claude Code? How to create Claude skills in Claude Code covers the file. For all seven sharing methods side by side, see the best ways to share AI skills with a team.

The AI skill below turns a prompt or doc into a correctly formed skill, with a name and a "use when" description, ready to commit to the repository.

Questions

How do I share Claude skills with my team on GitHub?

For Claude Code users, commit the skills to the project's .claude/skills folder, or publish them as a plugin marketplace that teammates add once with claude plugin marketplace add owner/repo. For people who use Claude in the browser or desktop app, GitHub is only a download place: they upload each skill as a ZIP.

Do teammates get updates automatically?

Project skills update when people pull the repository. Marketplace plugins update through Claude Code's plugin updates. Skills uploaded as ZIPs to claude.ai don't update; each person uploads the new version.

How do I distribute skills to coworkers who don't use GitHub?

Upload them in their Claude account, deploy them to everyone on Claude Team or Enterprise, or serve them from a shared skill library their AI connects to, so nobody downloads anything.