Sharing with colleagues, and the directory
Admin provisioning is top-down. The other two ways are bottom-up, run by the person who made the skill rather than an administrator.
Sharing with specific colleagues
A person who built a skill can share it directly with named coworkers. The people they pick get the skill, and it shows up for them in a "Shared with you" area of their Claude settings. This is the person-to-person path: good for a skill a small group needs, before or instead of a full organization rollout.
Publishing to the organization directory
The wider bottom-up path is the organization directory. Someone can publish their skill to an internal directory, where any coworker can browse, find it, and install it themselves. It's an internal catalog of skills the team has built, opt-in on the finder's side.
Both are off by default, and that's the point
Here's the detail worth remembering: both of these sharing options are turned off by default. A skill you build is private to you until you take a deliberate action to share it or publish it. It does not leak to colleagues, and it does not appear in the directory, on its own.
That default is a safety feature, not an inconvenience. It means no skill becomes a team asset by accident. Every skill that reaches other people got there because a human chose to share it, publish it, or provision it. When you reach the governance lesson and start asking "who can put a skill in front of the team," this off-by-default behavior is the floor the answer stands on.
Sharing with colleagues, and the directory
Admin provisioning is top-down. The other two ways are bottom-up, run by the person who made the skill rather than an administrator.
Sharing with specific colleagues
A person who built a skill can share it directly with named coworkers. The people they pick get the skill, and it shows up for them in a "Shared with you" area of their Claude settings. This is the person-to-person path: good for a skill a small group needs, before or instead of a full organization rollout.
Publishing to the organization directory
The wider bottom-up path is the organization directory. Someone can publish their skill to an internal directory, where any coworker can browse, find it, and install it themselves. It's an internal catalog of skills the team has built, opt-in on the finder's side.
Both are off by default, and that's the point
Here's the detail worth remembering: both of these sharing options are turned off by default. A skill you build is private to you until you take a deliberate action to share it or publish it. It does not leak to colleagues, and it does not appear in the directory, on its own.
That default is a safety feature, not an inconvenience. It means no skill becomes a team asset by accident. Every skill that reaches other people got there because a human chose to share it, publish it, or provision it. When you reach the governance lesson and start asking "who can put a skill in front of the team," this off-by-default behavior is the floor the answer stands on.