To share skills with your team, commit them to the repository's .claude/skills/ folder, and everyone working in that repository gets them. For several repositories, bundle them in a Claude Code plugin and publish a marketplace your team adds once. On Claude Team and Enterprise plans, an Owner can also provision skills to the whole organization, and they also load in Claude Code for members signed in with their Claude account.
How do public skill repositories package skills for sharing?
Use This Skill lists every skill it finds in public GitHub repositories. On November 13, 2026, we cloned the default branch of each of the 47 repositories in the November 9 crawl (data/skills.json, 1,966 skills) and checked how each one is set up for others to install. Safety results come from the November 9 scan (data/scan.json).
| What we checked | Repositories | Skills in them |
|---|---|---|
Ship a plugin marketplace (.claude-plugin/marketplace.json at the root) |
27 of 47 | 705 |
| Plugin entries listed in those marketplaces | 174 entries | 652 skills sit in a folder a listed plugin loads |
The repository is itself a plugin (.claude-plugin/plugin.json at the root) |
11 | |
| No marketplace, so you copy folders by hand | 20 | 1,261 (864 of them in ComposioHQ/awesome-claude-skills) |
Skills committed under .claude/skills/ for the project's own team |
3 | 87 |
Commit .claude/settings.json that registers a marketplace and turns plugins on |
2 |
Read by script from each repository's default branch on November 13, 2026, against the skill paths recorded in the November 9, 2026 crawl. A skill counts as loaded by a plugin when its path sits under a skills folder that a relative-path entry in the same repository's marketplace points to; entries that fetch from another repository or from npm were not followed, so 652 is a floor.
Three things stand out.
- Most authors who want their skills shared publish a marketplace. Outside ComposioHQ's single large collection, 705 of the 1,102 listed skills come from repositories with a marketplace, which means a team can add them with one command instead of copying folders.
- Very few public repositories use the per-project route for their own team. Only 87 skills, in 3 repositories, live in a committed
.claude/skills/folder, and 78 of those are in one repository, Donchitos/Claude-Code-Game-Studios. - Pre-registering a marketplace for teammates is rare. Two repositories commit settings that register a marketplace and turn plugins on for anyone who trusts the folder: homeassistant-ai/skills and stablyai/orca.
Packaging does not change what is inside. Repositories with a marketplace held 673 clear, 23 review and 9 flagged skills; those without held 1,232 clear, 24 review and 5 flagged. When you share a skill, every teammate who uses it runs it, so check the folder first with the free skill check.
Which way of sharing should I use?
Each route reaches a different group of people. These details were checked on each official page on November 13, 2026.
| Route | Who gets the skills | What you do | Updates |
|---|---|---|---|
| Commit to the repository | Everyone who works in that repository in Claude Code | Put the skill in .claude/skills/<name>/SKILL.md and commit it |
Arrive with git pull; Claude Code picks up changes without a restart |
| Plugin marketplace | Anyone who adds your marketplace, across all their projects | Put skills in a plugin, list it in .claude-plugin/marketplace.json, and send the add command |
When the plugin's version changes, through /plugin marketplace update or auto-update once it is turned on |
| Claude organization settings | Everyone in a Claude Team or Enterprise organization, in Claude and in Claude Code | An Owner adds the skill in Organization settings, then Plugins & skills | Managed by Owners in Organization settings |
| Share with a colleague on claude.ai | The people or groups you choose | Share the skill from your own skills | Recipients get your updates automatically |
| Managed settings directory | Every user on machines your organization manages | Your organization deploys .claude/skills/ in the managed settings directory |
When your organization updates those files |
The first two need nothing but git. The third and fourth need a Team or Enterprise plan; group-specific provisioning and skill scanning are Enterprise features, according to the Claude Help Center.
How do I share a skill through the repository?
Create the folder, add the skill, and commit it:
.claude/skills/release-notes/SKILL.md
The Claude Code docs describe the project location as loading in "sessions in this repository" and add: "Commit it so your team gets it too." Claude Code also loads .claude/skills/ from every parent directory up to the repository root, so a skill at the root still works when someone starts Claude Code in packages/frontend/. A skill in a nested .claude/skills/ folder loads the first time Claude reads or edits a file in that folder.
One catch: in Claude Code, personal skills take precedence over project skills. If a teammate has their own release-notes in ~/.claude/skills/, theirs runs instead of yours. Give team skills distinct names. Committed skills are also not available in a project's cloud threads, according to the same page.
How do I share skills across many repositories?
Publish a plugin marketplace. A marketplace is a marketplace.json file at .claude-plugin/marketplace.json; name, owner and plugins are required, and each plugin entry needs a name and a source. Your teammates then run, inside Claude Code:
/plugin marketplace add your-org/your-marketplace
/plugin install your-plugin@your-marketplace
Skills from a plugin appear as /plugin-name:skill-name, so they never collide with a teammate's personal skills.
A plugin can also carry subagents, hooks and MCP servers, and some of those run code by themselves. Our guide to Claude Code plugins vs skills shows what 171 public plugins contain and how to check one before you install it.
To have the marketplace registered for everyone in one repository, the Claude Code docs say to run claude plugin marketplace add your-org/your-marketplace --scope project once and commit the .claude/settings.json it writes. Claude Code then registers the marketplace for each teammate who trusts the folder. For a whole company, an administrator can set extraKnownMarketplaces and enabledPlugins in managed settings instead.
For a private repository, Claude Code runs git on each person's machine with prompts turned off, so each teammate needs credentials already stored: an SSH key loaded in ssh-agent, or on GitHub, gh auth login followed by gh auth setup-git. The docs note that marketplace.json has no field for a token.
Two release habits save confusion. Users get a new copy only when the plugin's version changes, so either raise version on every release or leave it out of both plugin.json and the marketplace entry so users track your commits. And background auto-update is off until each user or an administrator turns it on.
How do I share skills across a Claude organization?
On Team and Enterprise plans, an Owner goes to Organization settings, then Plugins & skills, clicks Add, and uploads a .zip with a SKILL.md or creates a skill from a name and description. The Help Center says the skill "is immediately provisioned to all users in your organization," it is on by default, and each user can turn it off. Code execution and Skills must be turned on in the Policy tab first.
Members can also share a skill with chosen colleagues. Shared skills are view-only and stay off until the recipient turns them on. Organizations can also run a library with a publishing setting of Requires review, Open or Off. Provisioned skills load in Claude Code for users who sign in with their Claude account, unless an administrator sets syncClaudeAiSkills to false.
What about Codex, Cursor and Gemini CLI?
The repository route works for any agent that reads skills from a folder in the project, but each reads its own folders. Our guide to skills in Codex, Cursor and Gemini CLI lists them. The plugin marketplace and the organization settings described here are Claude features. For instructions every agent should follow, compare skills with project files in AGENTS.md, CLAUDE.md and SKILL.md.
What should I check before I share a skill?
Read the whole folder, not only SKILL.md, because a skill's scripts run on your teammates' machines when the agent runs them, and its reference files load into the conversation like SKILL.md does; what a malicious skill can do shows what to look for. Run the folder through the skill check, or let your agent do it with the MCP connector, which returns the scan result for any listed skill. If you copy a skill from GitHub into your team's repository, pin the commit you checked, as described in how to install a skill from GitHub.
How we counted
The repository list and skill paths come from data/skills.json (crawl of November 9, 2026: 1,966 skills, 47 repositories). On November 13, 2026, each repository was cloned at depth 1 from its default branch. We looked for .claude-plugin/marketplace.json and .claude-plugin/plugin.json at the root, parsed each marketplace's plugins array, and matched skill paths to the skills folders of relative-path entries (including a skills field on the entry or in the plugin's plugin.json). Committed project skills are those whose crawl path includes .claude/skills/. Settings files were searched for extraKnownMarketplaces and enabledPlugins. Scan results come from data/scan.json (November 9, 2026). Repositories can change between the crawl and the check, so a few counts could differ slightly today.