Last reviewed:
SkillReg vs Claude Code Plugin Marketplaces and GitHub Skill Repos
Facts about third-party tools were checked on October 16, 2026. Each one links to a numbered, dated source at the bottom of the page. Anything we could not check is marked "not verified".
Many teams start sharing skills in one of two ways: a GitHub repository full of SKILL.md files, or a Claude Code plugin marketplace that bundles those skills into plugins. Both are Git-based and both work well up to a point. This page explains how they work, what Claude Code lets administrators control, and when a dedicated registry such as SkillReg adds something.
What a Claude Code plugin marketplace is
A plugin marketplace is a catalog file, .claude-plugin/marketplace.json, that lists plugins and where to fetch them [1]. Claude Code's settings types describe the places a marketplace can come from [1]:
- a GitHub repository (
owner/repo) or any Git URL, where the catalog defaults to.claude-plugin/marketplace.json; - a direct URL to a
marketplace.jsonfile, an npm package that contains one, or a local file or directory; - marketplace entries declared inline in settings.
A plugin entry in marketplace.json can declare the skills it ships, for example "skills": ["./skills/review", "./skills/test"] [2]. A plugin's version comes from its plugin.json manifest or its marketplace entry, and Claude Code notes that this value is "plugin-author-controlled" [1].
What administrators can control
Claude Code ships real governance settings for marketplaces [1]:
extraKnownMarketplacesadds marketplaces for a repository, "typically used in repository .claude/settings.json to ensure team members have required plugin sources".strictKnownMarketplaces, set in managed settings, is an "enterprise strict list": only the listed sources can be added, and a GitHub entry may use theowner/*wildcard. It is "a policy gate only" and does not register marketplaces by itself.blockedMarketplacesblocks listed sources, andstrictPluginOnlyCustomizationcan block non-plugin sources of skills, agents, hooks or MCP configuration.enabledPluginsturns plugins on or off withplugin-id@marketplace-ididentifiers.
What GitHub skill repositories are
The simplest form of sharing is a Git repository with one folder per skill. Tools read these repositories directly: the skills CLI installs from owner/repo and also reads .claude-plugin/marketplace.json "for compatibility with the Claude Code plugin marketplace ecosystem" [2].
anthropics/skills is a public GitHub repository of skills under the anthropics organization, the same GitHub organization that publishes Anthropic's Claude Agent SDK [1]. Third-party tools use it as their install example: skillkit install anthropics/skills [3], and smithery skill add anthropics/frontend-design [4]. Its exact contents, license and update policy are not verified on October 16, 2026: we could not read GitHub for this review. Treat it as a high-quality public source to learn from and copy, not as a place to host your own team's skills.
For the generic pros and cons of keeping skills in Git, see SkillReg vs Git Repos.
What SkillReg adds
SkillReg is a private registry for your organization's SKILL.md skills, independent of any single agent:
- Versions are published to the registry (
skillreg push --versionor--bump) and installs resolve semver ranges (Installing Skills). - The same skill installs for Claude, Codex and Cursor (
skillreg pull --agent all) or from the desktop app. skillreg import-github owner/repoimports an existing GitHub path that contains aSKILL.md(CLI Reference).- Security scanning on every publish on all plans, including Free (advanced checks on Enterprise); basic audit logs from Team, full audit logs on Enterprise; SSO and approval workflows on Enterprise (pricing).
Side-by-side comparison
| Question | Claude Code plugin marketplace | GitHub skill repository | SkillReg |
|---|---|---|---|
| Unit you share | Plugins, which can bundle skills [2] | Folders with a SKILL.md [2] | Individual versioned skills |
| Where it lives | Git, URL, npm package or local path [1] | Your Git host | SkillReg registry, per organization |
| Agents | Claude Code; the skills CLI can also read the catalog [2] | Any agent, through a tool that installs from Git [2] | Claude, Codex and Cursor |
| Versions | Version string set by the plugin author [1] | Git history; no registry of versions | Registry versions, semver ranges on install |
| Admin control | Allow list, block list and per-repository marketplaces in managed settings [1] | Repository permissions of your Git host | Organization membership, tokens with read, write or admin scopes |
| Server-side scanning and audit log | Not documented in the settings types (not verified) [1] | Depends on your Git host (not verified) | Scanning on every publish, all plans (advanced on Enterprise); audit logs from Team |
When to use which
Use a Claude Code plugin marketplace when your team works only in Claude Code and wants to ship skills together with agents, hooks or MCP configuration in one plugin [1]. The managed settings above give administrators a clean allow list.
Use a GitHub skill repository for open-source skills, or when one repository and Git permissions are all the governance you need.
Use SkillReg when the same skills must reach several agents, when you need to know which version each person installed, or when security scanning and an audit trail are required.
Using both
These options combine well. Keep public or Claude Code-only plugins in a marketplace and list it in extraKnownMarketplaces. Host your internal skills in SkillReg and install them for Claude Code, Codex and Cursor. To move an existing repository, run skillreg import-github owner/repo once per skill path.
Related comparisons
Sources
- @anthropic-ai/claude-agent-sdk 0.3.301 on npm, Claude Code settings types in sdk.d.ts (repository anthropics/claude-agent-sdk-typescript) (extraKnownMarketplaces, strictKnownMarketplaces, blockedMarketplaces, strictPluginOnlyCustomization, enabledPlugins). Version published 2026-10-15; checked 2026-10-16.
- skills 1.7.2 on npm, README of the skills CLI (repository vercel-labs/skills), sections "Source Formats", "Skill Discovery" and "Plugin Manifest Discovery". Version published 2026-10-09; checked 2026-10-16.
- skillkit 1.24.0 on npm, README, "Quick Start". Version published 2026-04-21; checked 2026-10-16.
- @smithery/cli 4.11.1 on npm, README, "Examples". Version published 2026-04-30; checked 2026-10-16.