[FEATURE] Link a source control repo as the source for organization skills
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) 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 comm
Posted by KyleNesium on Feb 25, 2026, 8:28 PM
Tags
Related issues
- ⚠️ PHP CVEs. Update required!
- I think RTS could continue to work if someone made a massive leap of faith and put all the modern infra around it that a AAA extraction s...
- RFC: Pluggable SessionDB Provider — PostgreSQL, MySQL, and Beyond
- v2.1.113+ broken on Termux/Android: native binary requires glibc, no JS fallback
- I’m firmly anti-Tahoe and haven’t updated, and I’ve started to find Apple despicable.
- Feature Request: Option to disable paste text collapse in input field
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
reliability (Sysadmin)
⚠️ PHP CVEs. Update required!
I think RTS could continue to work if someone made a massive leap of faith and put all the modern infra around it that a AAA extraction s...
RFC: Pluggable SessionDB Provider — PostgreSQL, MySQL, and Beyond
v2.1.113+ broken on Termux/Android: native binary requires glibc, no JS fallback
I’m firmly anti-Tahoe and haven’t updated, and I’ve started to find Apple despicable.
[FEATURE] Link a source control repo as the source for organization skills
Feature Request: Option to disable paste text collapse in input field
We went down the WASM sandboxing rabbit hole at Gobii when building our agent infra.
[FEATURE] Link a source control repo as the source for organization skills
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) 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 comm
Comments (0)
No comments yet. Start the discussion.