How to share Claude skills with your team: Claude app, Claude Code, Codex and ChatGPT

What are the ways to share a skill with your team?

To share Claude skills with your team, you either add them to your Claude organization (Team and Enterprise plans) or put the skill folders in a Git repository that everyone uses. For larger rollouts in Claude Code, you package the skills as a plugin in a private marketplace.

Each route fits a different tool and audience. Pick by where your team works:

One rule applies everywhere: custom skills don't sync between surfaces by default. Anthropic's Agent Skills overview says skills uploaded to claude.ai must be uploaded to the API separately, and Claude Code skills are filesystem based and separate from both. Plan for the tools your team actually opens every day.

How do Claude Team and Enterprise owners provision skills?

Owners can add a skill once and have it appear for every member. Anthropic's help article on provisioning skills for your organization gives these steps:

1. Go to Organization settings > Plugins & skills, open the Policy tab and make sure both code execution and Skills are on. Skills need code execution to run.
2. Click Add in the upper right.
3. Upload a .zip that contains the skill folder with its SKILL.md, or create one by typing a name and description.
4. The skill appears for all members right away under Customize > Skills.

Provisioned skills are on by default, but each person can switch one off. They also load in Claude Code for anyone who signs in with a Claude account. To stop that, an admin sets syncClaudeAiSkills to false in Claude Code managed settings.

On Enterprise you can target a group instead of everyone: bundle the skills into a plugin and assign the plugin to that group. Owners can also turn off User-created skills on the Policy tab if only approved skills should exist. Provisioned and built-in skills stay available when that switch is off.

From the same Policy tab, owners decide how member submissions reach the shared library:

• Requires review: an owner approves each submission and picks how it's offered.
• Open: submissions publish without review. On Enterprise with security scanning on, they list once the scan passes.
• Off: the Publish to org button is hidden, though owners can still add skills directly.

Reviewers work from the Requests tab. They see the exact submitted version, every file, scan results and what changed since the last published version, then choose Approve or Request changes.

How do members share a skill with colleagues?

Members on Team and Enterprise can share a skill they made without publishing it to everyone. The steps from Anthropic's Use skills in Claude article:

1. Go to Customize > Skills and find your skill.
2. Click the ... menu next to it and choose Share.
3. Enter people's names or emails, or pick a group (Enterprise only).
4. Click Share.

The Skill sharing toggle in the Policy tab controls this. It is on by default for Team plans and for Enterprise plans that haven't set a skills preference, and sharing with a group also needs the Share with groups toggle, which is off by default. Shared skills are view-only: colleagues can use the skill but not edit it, and they get your new version the next time they use it. Access ends when you remove it or when someone leaves the organization.

To give a skill to the whole organization instead, open it and click Publish to org. If review is required, you choose how it's offered: Available to install, Installed by default or Required. Once published, an approved new version reaches everyone automatically, and people stay on the current version until the update is approved.

How do you share Claude Code and Codex skills through a repo?

For developer teams, the simplest route is a folder in the repository you already share. The Claude Code skills docs list project skills at .claude/skills/<skill-name>/SKILL.md and say to commit the folder "so your team gets it too."

your-repo/
├── .claude/skills/
│   └── release-notes/
│       └── SKILL.md        Claude Code reads this
└── .agents/skills/
    └── release-notes/
        └── SKILL.md        Codex reads this

Codex looks in a different place. OpenAI's Codex skills docs list repository skills in .agents/skills, scanned from the working directory up to the repo root, plus $HOME/.agents/skills for each user and /etc/codex/skills for machine-wide defaults set by an admin. A team on both tools needs the skill in both folders, or an install step that copies it.

Three things to know before you rely on repo skills in Claude Code:

• Name clashes: when an enterprise, personal and project skill share a name, enterprise wins over personal, and personal wins over project. A teammate's personal copy can quietly shadow the repo version.
• Org-wide copies: admins can place skills in the managed settings directory (for example /etc/claude-code/.claude/skills/ on Linux) so they load on every managed machine.
• Review allowed-tools: a checked-in skill can pre-approve tools for the turn that invokes it. Read that field in pull requests the same way you'd read a script.

When should you package skills as a plugin marketplace?

Move from a repo folder to a plugin when the same skills need to reach many repositories, or when you want versioned releases. A marketplace is a Git repo with a .claude-plugin/marketplace.json that lists your plugins, as described in Anthropic's guide to creating a marketplace. The repo can be private, and anyone with read access can install from it.

# Each teammate, once
claude plugin marketplace add your-org/team-skills
claude plugin install release-tools@team-skills

# Or register it for everyone in one repo: run once, then commit .claude/settings.json
claude plugin marketplace add your-org/team-skills --scope project

For a company-wide rollout, an administrator sets extraKnownMarketplaces and enabledPlugins in managed settings so the marketplace and its plugins install at each person's next session, per Anthropic's page on managing plugins for your organization. The same page covers strictKnownMarketplaces, an allowlist that limits which marketplaces people can add.

Updates need one decision. Background auto-update is off by default for marketplaces you run, so people get changes when they run claude plugin update or turn on Enable auto-update in /plugin. Either bump the plugin's version on every release or leave version out so users track commits. Our Claude Code plugin marketplace guide walks through the file format.

How do you share skills in a ChatGPT workspace?

ChatGPT has its own workspace skills, separate from Claude's. OpenAI's skill controls page describes a ChatGPT workspace skill as the way to share or install an approved workflow through supported workspace features, governed by the workspace's skill permissions and lifecycle controls. For the current sharing steps and plan availability, that page points to OpenAI's Skills in ChatGPT help article.

Keep two OpenAI rules in mind. First, ChatGPT workspace skills, local filesystem skills and plugins are separate systems: the same page says workspace controls don't install filesystem skills or plugins, and moving a skill doesn't carry over workspace ownership or sharing. Second, to reach both ChatGPT and Codex at once, OpenAI's Build skills guide points to plugins, which are distributed through a plugin directory shared by the two products.

How do you keep shared skills reviewed and up to date?

Sharing is easy. Keeping twenty shared skills correct is the real work. A few habits help on every route:

1. One source of truth. Keep the master copy of each skill in Git, even if you also upload it to the Claude app. Uploads are snapshots; a repo has history and diffs.
2. Review changes like code. Use pull requests for repo skills and the Requires review policy for org skills. Reviewers should read every file, scripts included. Our Agent Skills security guide has a checklist.
3. Decide who can publish. In the Claude app that's the Publishing policy and the User-created skills switch. In Claude Code it's who can merge to the marketplace repo.
4. Pin what you can't review often. Plugin entries can point at a Git ref or sha, so a marketplace holds people on a version you've checked.
5. Prune. Skills nobody triggers still cost context. In Claude Code, /skill-doctor (v2.1.252 or later) lists skills that have never been invoked.

New hires are where shared skills pay off most; see Claude Code team onboarding for the rest of that setup.

Keep your team's skills in one repo

If your team's skills live in one GitHub repo, every route above gets simpler: the repo is what you review, what you zip for the Claude app and what you install from. Kipt keeps prompts and skills as Markdown in a private GitHub repo you own, imports skills from a GitHub link, a folder or a .zip, and installs every skill into Claude Code or Codex with one command: npx skills add https://github.com/<you>/<repo>.git --all -g. To turn a prompt your team already uses into a valid skill first, try the free SKILL.md generator.