[FEATURE] Link a source control repo as the source for organization skills
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Currently the only way to manage org-level skills is uploading them individually through the Claude.ai admin console. This sorta works when you have a handful of skills, but even then you're manually re-uploading after every revision. Once you get to 20-30+ skills with multiple contributors, it becomes difficult to manage — there's no version history, no review process, and no easy way to roll back a bad change.
The plugin marketplace system supports git repos, but it's user-configured rather than admin-controlled. The extraKnownMarketplaces managed setting that could help with this is currently broken (#16870), and there are open issues with marketplace auto-update (#26744) and the upload process itself (#16625, #27979).
Org skill management feels like an incomplete feature — the foundation is there but it's missing the tooling to make it practical at scale.
Proposed Solution
Allow org admins to link a source control repository as the skill source for their organization. Any git remote would work — GitHub, GitLab, Bitbucket, Azure DevOps, self-hosted Gitea, etc.
Admin side:
- In org settings, connect a git repo URL (public or private) as the skill source
- Pick a branch, tag, or commit to deploy from
- Preview changes before syncing
- Sync manually, or optionally auto-sync on push via webhook
User side:
- Org skills from the linked repo appear automatically — no per-user setup needed
- Indicator when newer skills are available
- One click or command to pull the latest
CI:
- Claude Code in CI picks up the same org skills automatically
- Can pin to a specific commit for reproducibility
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Configuration and settings
Use Case Example
Our team maintains around 20 org skills for code review standards, security checks, and deployment workflows. Today someone edits a skill locally, uploads it through the admin console, and nobody reviews the change. If something breaks, we piece together what happened through Slack.
With a linked repo, skill changes would go through the same merge request and review process as any other code. On merge, the org's skills update. If something's wrong, revert the commit. Standard development workflow applied to skills.
Additional Context
Related: #25771 — Programmatic skill deployment via CLI/API (complementary — covers the CI/CD push side, this covers the persistent source-of-truth side)
39 Comments
Would love to see this please
Bumping this as we would really like it, and it feels like a must have feature.
must have for us also
This would make my life so much easier provisioning skills to devs in my org.
Bumping - We need to roll out skills across the org and this feels like a must have to enable this
A must have, as users uploading skills which can contain scripts with uncontrolled intents is unacceptable.
Would also be highly interested in this.
agreed with all comments above. this is a must have
We have 2k licensed users trialling Claude.
This would probably be our number 1 feature request right now.
This IS my number one feature request. Without the ability to put our agent skills into Azure DevOps and publish them from there, we cannot effectively use skills.
UP
Bump, now it is a mess - zip files for skills, and in the same settings, the GitHub connection. Cowork plugins have a different format.
Bump !
Bump too!
This is a major concern for us, as the skills uploaded in the admin panel have no connection to their original sources.
This would be huge. Also subagents... 🙏
I guess skills wrapped in plugins could be used as a workaround...
An interesting wrinkle is that complex skills (with scripts and sub-agent invocation) do not work exactly the same on Claude.ai
I have tried to work around this by having a build process that generates web- and claude-code versions of each skill. Is there an officially supported way to do that, however? (or maybe they'll make Claude on the web more Claude Code like)?
My attempt: https://github.com/noahlz/claude-plugins/blob/main/.github/workflows/release-web-skills.yml
@klutchell marketplace plugins in chat would be, in our case preferable. Where did you quote that text from?
@basileaw In this marketing email sent to our org admins, from Anthropic.
<img width="596" height="443" alt="Image" src="https://github.com/user-attachments/assets/1bf607ba-266a-4007-be56-2a7f870f9799" />
I haven't seen any updated docs yet, and it doesn't link to a blog post or anything.
I'm using the share button as a workaround right now; it's functional, but
not remotely sufficient to our needs.
this output?")
and for what work item?")
version of the skill out to all of the engineers")
compare against the previous version?")
Skills are effectively the code that creates the code. Unless we treat them
like code throughout their lifecycle, we cannot effectively use them at
scale.
On Fri, May 29, 2026 at 7:52 AM Kyle Harding @.***>
wrote:
Bump!
This would be a very helpful feature for org-wide version controlled publication of skills.
This is desperately needed Anthropic, our skills often reference generated files and those need to be updated frequently. Without programmatic deployment we are limited to static skills.
++
Need this feature
This is a HUGE gap in the product currently. Anthropic needs to deliver this ASAP!
We absolutely need this!
++ This feature would be actually awesome
Can't believe Claude.ai does not have this yet... This needs to be added fast
plz add this
++ This is a must have. Managing a growing skill library by manually uploading .zip files does not scale and it's a poor user and developer experience. At a minimum, providing a programmatic option (skill endpoint) so we can control the deployment would be a big step forward.
Bump! 👍 this would be super helpful.
Was excited to see https://platform.claude.com/docs/en/build-with-claude/skills-guide#creating-a-skill but then disappointed this is only for the workspace level. And still nothing for the org level.
+1 please help, this is really helpful for stronger governance of our org deployment.
+1 for this. It is a must have for my organization !
+1 for this.
Our organisation is currently lacking this. We can only achieve it with plugins through the marketplace exposed in GitHub
+1
I need to upload ZIP files manually ... wtf!
+1
Really needed
I can confirm that a workaround exists. Create a private/internal repo with your skills, and include the plugin manifests so it can be synced with your organization under Plugins. This will expose those skills to your org.
Thank you for building Skills. A skill that carries a whole working practice into every session is the most useful thing in my setup, and I don't take it for granted.
One data point from the individual-user side, since the thread is mostly org admins.
My skills are personal, on my own account, and I work almost entirely in Cowork. Cowork loads the skills enabled on my claude.ai account and doesn't read
~/.claude/skills/, so the filesystem route that makes Claude Code skills easy to version never reaches the surface I actually work in. My skills live in a git repo locally. Shipping an edit means uploading a zip through the browser, one skill at a time.I tested the plugin-marketplace route as a workaround: git repo, marketplace, installed plugin. Plugin-provided skills do load in Cowork, so that half works. But a pushed version bump didn't reach a fresh session on its own — it still read the old version — so it trades a browser upload for a manual pull.
So this request would help me too, one scope down: a repo as the source for personal skills, not only organization ones. Same shape, same reasons — version control, review, and a push instead of a hand upload.
Happy to test anything.