Skip to main content
A skill is a set of instructions that teaches Claude how to use a specific tool or follow a specific process (for example, which Datadog endpoints answer which questions, or your org’s incident-response runbook). Claude Tag uses the same skills format as Claude Code. A plugin bundles one or more skills together. You can upload skills one at a time in the console, but putting them in a git repository means Claude can open pull requests to improve them from what it learns working in your channels. You review the PR; once merged, every channel picks up the update.

​
Set up the skills repository

1

Create the repository

A private or internal GitHub repository, laid out as a Claude Code plugin marketplace: a .claude-plugin/marketplace.json file at the root that lists each plugin, and one folder per plugin. Each plugin bundles one or more skills. A public repository can’t be selected in the next step; fork it into a private one first.
2

Register the repository as a plugin marketplace

For a github.com repository, the GitHub connector must be enabled for your organization. On the Plugins page at claude.ai/admin-settings/plugins, click Add plugins and choose Sync from GitHub. Select the repository, leave Sync automatically on (the default), and click Create.
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 tab, toggle on the plugins from your new marketplace; each is off until you enable it. See Attach plugins.
You’ll see: the repository appears in the bundle’s Repositories list, and the marketplace’s plugins appear in the bundle’s Plugins tab, each labeled with the marketplace name.

​
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:
Or set a routine that sweeps a channel’s corrections into proposed updates:

​
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.