Agent skills marketplaces › Sharing skills across a team

An agent skills registry for your team: five ways to share skills, and what each costs

Most teams should start by committing skills to the repository (.agents/skills/ for Codex, Cursor and Copilot, .claude/skills/ for Claude Code) and reviewing them in pull requests: it's free and every major agent reads them. When skills must reach every repo or machine, use the agent's private marketplace: a Claude Code marketplace required through managed settings, a Cursor team marketplace, or a GitHub marketplace imported into a ChatGPT workspace for Codex. Tessl adds a cross-agent registry with evals; its Enterprise plan adds install policies.

Read in Anthropic's, Cursor's, OpenAI's and Tessl's documentation and pricing pages on November 13, 2026.

The five ways, side by side

1. Commit skills to the repository

A skill is a folder, so the simplest registry is your repo. Put shared skills in .agents/skills/ (read by Codex, Cursor, Copilot and most others) and, for Claude Code, .claude/skills/, which Cursor and Copilot also read. Changes go through pull requests, so a new script gets the same review as code.

To pull in public skills without copying them by hand, the skills CLI records each one's source commit and a hash of its files in skills-lock.json; skills check and install --frozen-lockfile compare what's on disk with that hash, which makes a CI check easy. The limit: skills live per repository, so a skill every repo needs has to be copied or vendored into each.

2. A private Claude Code marketplace

A marketplace is a git repository with a .claude-plugin/marketplace.json that lists plugins, and plugins carry skills. The repository can be private; each user needs read access, and Claude Code clones it with their stored git credentials. Two ways to roll it out:

• Per repository: extraKnownMarketplaces and enabledPlugins in the repo's .claude/settings.json register the marketplace once a contributor trusts the folder; each contributor still runs claude plugin install name@marketplace --scope project.
• Every machine: the same two keys in managed settings, delivered from the claude.ai admin console, MDM or a managed-settings.json file. Claude Code installs the plugins at the next session start, and users can't turn them off.

To keep other skills out, the managed strictKnownMarketplaces allowlist limits which marketplace sources plugins may come from, blockedMarketplaces blocks named ones, and disableSideloadFlags rejects --plugin-dir. The allowlist doesn't cover plain SKILL.md folders; strictPluginOnlyCustomization blocks skills from user and project folders when only plugins should load. Anthropic's docs list what this can't do: there's no per-group targeting in one policy, and no key hides /plugin.

3. A Cursor team marketplace

On Cursor's Teams plan (one team marketplace) and Enterprise (unlimited), an admin creates a marketplace or imports one from GitHub, GitLab, Bitbucket or Azure DevOps. Each plugin gets a mode: Required (always installed, can't be removed), Default On (installed, developers can opt out) or Default Off. For a GitHub import, "Serve marketplace from Cursor" keeps a synced copy so teammates don't need access to the source repo. Plain skills folders need a .cursor-plugin/marketplace.json to import; more in Cursor skills.

4. A ChatGPT workspace marketplace, for Codex

OpenAI's plugins work in both ChatGPT and Codex, and a plugin can bundle skills. In a Business, Enterprise or Edu workspace, admins import a team's GitHub marketplace under Admin › Plugins › Add › Import marketplace, press Sync now to pull updates, and set each plugin to Installed by default or Available to install. Sharing and publishing to the workspace directory are separate permissions, set per role. In Codex CLI, workspace plugins appear under /plugins; skills arrive in the next new session.

5. Tessl, a registry across agents

Tessl is a registry built for skills rather than added to a package manager: publish and install skills and plugins for several agents with one CLI (npx tessl i), with reviews, evals and Snyk security scores on each. Free covers unlimited publishing and installing with 1,000 credits a month; Team is $100 a month (5,000 credits, role management, not priced per seat); Enterprise adds install and publish policies, mandated org-standard skills, audit logs, SAML SSO and self-hosting. It's the pick when several agents are in use and someone has to approve what gets installed.

Hosted registries from security and platform vendors

Several companies that already store a team's packages now store skills too. Each was in beta or new on November 13:

• JFrog Artifactory: Skills is a beta package type, compatible with ClawHub's protocol; jf agent skills publishes, searches and installs them from a private repository.
• Chainguard: a public catalog of more than 1,000 hardened community skills, and a private Skills Registry (beta) where your own skills are uploaded, hardened and installed with chainctl.
• TrueFoundry: a versioned skills registry inside its AI Gateway, for TrueFoundry agents, Claude Code and Cursor.
• Google Cloud: a Skill Registry in its agent platform, for agents built on Google Cloud more than for coding agents.

They make sense when the company already runs that vendor's platform. None of them is needed to share skills between a few engineers.

Then check what gets used

Sharing a skill doesn't mean anyone runs it, and in Claude Code every installed skill's description costs context on each turn. The options, by what they count:

Zest is made by the company that publishes this site. It isn't a registry: it doesn't install skills, version them or enforce policies, and it needs GitHub for the pull-request side. Its CheatCodes pull reusable prompts, workflows and skills out of sessions so a practice one engineer found can spread. For a team of ten, Pro is $49 with 5 seats plus five $19 seats ($144), or Max is $149 with 10.

Rules that hold up

• Review skills like code. Read the scripts, frontmatter and hooks before merging; the ten checks are in Are agent skills safe?
• Pin versions. A commit in skills-lock.json, a sha on a marketplace source, or a Tessl version, not "latest".
• Allowlist sources where your agent supports it, starting with the official marketplace and your own.
• Prune. Remove skills nobody has run in a month.

Where to find public skills worth adding is on the marketplace comparison.