This article explains how organization owners can provision skills for everyone in their organization, and how to scope skills to specific groups using plugins. Provisioning skills lets you distribute approved workflows and capabilities across your organization from one place.
Organization-wide skill management is available to Team and Enterprise plans.
Prerequisites
Before you can provision skills for your organization, you must navigate to Organization settings > Skills and enable both Code execution and file creation and Skills by toggling them on. Skills require code execution to function, so if code execution is disabled, skills will not be available.
Provision skills for everyone
When you upload a skill through organization settings, it becomes available to everyone in your organization in Customize > Skills. Individual members no longer need to upload the same skill themselves.
To provision a skill:
Navigate to Organization settings > Skills.
In the Organization skills section, click "+ Add."
Select a .zip file containing your skill (must include a SKILL.md file).
The skill is immediately provisioned to all users in your organization.
Admin-provisioned skills are enabled by default for everyone, but members can toggle individual skills off if they choose. This gives your organization consistent, approved workflows while letting members customize their own experience.
Provision skills to specific groups
Provisioning a skill through Organization settings > Skills gives it to everyone. To give a skill to only some members, bundle your skills into a plugin and assign that plugin to a group. The group's members see those skills, and members outside the group don't.
For example, if you have 10 skills for your marketing team, add them to a plugin and assign it to the marketing group. Only that group gets those skills.
Skills provisioned this way appear in chat, on the web and the Chat tab in Claude Desktop, as well as in Cowork. Group targeting you've already set up for Cowork carries over to chat with no extra steps.
To set this up, see Manage plugins for your organization.
Control skill sharing between members
In addition to provisioning skills top-down, you can let members share skills they've built with each other. Two independent toggles control this:
Skill sharing: Members can share a skill with specific colleagues. Recipients see the skill in the Shared with you section of their skills list.
Share with organization: Members can publish a skill to the organization directory, where anyone can find and install it.
Both toggles are off by default. You can enable either or both in Organization settings > Skills.
Note: Shared skills are view-only. Recipients can enable and use a shared skill but can't edit its contents.
How shared skills differ from provisioned skills
| Owner-provisioned | Shared peer-to-peer | Shared org-wide |
Who can share | Owners only | Any member (if enabled) | Any member (if enabled) |
Where it appears | Everyone's skills list | Recipient's "Shared with you" section | Organization directory |
Can recipients remove it? | Disable only | Disable or delete | Disable only |
Requires owner approval? | Owner uploads directly | No | No |
Important: There's no approval workflow for org-wide sharing. If you enable Share with organization, any member can publish a skill to the directory without review. Consider enabling peer-to-peer sharing only if this is a concern.
Monitor sharing activity
Skill sharing events are captured in the audit log and Compliance API as role_assignment events. You can see who shared a skill, with whom, and whether it was peer-to-peer or organization-wide.
The audit log doesn't capture the contents of shared skills—only the share event itself. There's no admin dashboard to browse or inspect the contents of skills shared between members.
How members see provisioned and shared skills
Skills appear for each member in Customize > Skills, organized into three sections:
Personal skills: Skills the member has created or uploaded.
Shared with you: Skills colleagues have shared directly with a member. These appear grayed out until enabled.
Organization skills: Skills an owner has provisioned and skills members have shared organization-wide. Members install these from the directory.
Owner-provisioned skills are marked with a visual indicator so members can distinguish them from other skill types. Members can click on any skill to preview its contents and description.
For more on how members browse and install from the directory, see Browse skills, connectors, and plugins in one directory.
Manage and remove provisioned skills
The Organization skills section in Organization settings > Skills displays all skills provisioned for your organization. Use search and the section headings to navigate them.
To remove a skill from your organization, locate it in the Organization skills list and select the option to remove it. Once removed, the skill will no longer appear in members' skills lists in Customize > Skills.
Note: Only owners can add or remove organization-wide skills. Individual users cannot delete provisioned skills, though they can toggle them off for their own use.
Best practices
Test skills before provisioning: Upload and test skills on your own account first to verify they work as expected before distributing them organization-wide.
Scope specialized skills to groups: When a skill is only relevant to one team, bundle it into a plugin and assign it to that group instead of provisioning it to everyone.Use descriptive names: Give skills clear names that help users understand their purpose at a glance.
Write clear descriptions: The skill's description helps Claude determine when to use it automatically. Ensure descriptions accurately reflect what the skill does.
Consider default status carefully: Enable skills by default when they're broadly useful to most users.Keep specialized skills disabled by default for the members who don't need them.
Decide on sharing deliberately: Organization-wide sharing has no approval step. If you want to review skills before they reach everyone, keep organization-wide sharing off and ask members to submit skills to an owner for provisioning instead.