Set up the skills repository
1
Create the repository
A new GitHub repository in your organization, with one folder per plugin. Each plugin bundles one or more skills.
2
Register the repository as a plugin marketplace
In claude.ai admin settings, add the repository as an organization plugin source and leave Sync automatically on (the default).
3
Grant Claude write access to the repository
Open an Access bundle, go to its Repositories tab, and add the repository. The Claude GitHub App must already be linked to your GitHub organization; see Configure GitHub access.
4
Attach the plugins to a scope
In the same bundle’s Plugins section, select + and add your new marketplace. See Attach plugins.
How updates propagate
Once the repository is set up, Claude can propose changes and they reach channels automatically after you merge:
Every skill change reaches channels only after a human approves the merge; Claude opens the PR, you merge it.
Prompt Claude to propose updates
Claude won’t open skill PRs unprompted. Ask in the channel when something it learned should stick:Why a repository instead of uploading skills
You can also upload individual skills in the console without a repository. The repository pattern is worth the setup because Claude can propose changes to it, every change goes through version control and code review, and you can attach the same skills to multiple bundles without uploading them again.What belongs in the repository
Skills in the repository reach every channel under the scope.
Related resources
- Attach plugins: how plugins and skills load into a scope
- Configure GitHub access: granting Claude write access to a repository
- What Claude Tag remembers: when channel memory is the right place instead