Admin provisioning: top-down rollout
The first way a skill becomes a team asset is an administrator pushing it out. This is for skills the whole organization, or a whole department, should run.
Organization-wide skill management is a feature of the Claude Team and Enterprise plans. On those plans, an administrator can upload a skill through the organization settings. Once they do, that skill becomes available to everyone in the organization. People find it in their Claude settings, under Customize, then Skills. They don't have to hunt for it or install anything; the admin's upload provisioned it to everyone.
Two control points matter here, and they're the reason this is the safe default for important skills.
The admin gate. On Team and Enterprise plans, an administrator enables Skills for the organization before anyone can use them at all. Skills are not just on by default. Someone with authority turns the feature on, and that same someone controls what gets pushed out.
Central control. Because provisioning runs through the admin, the organization has one place to manage skills: push them out, restrict them, and audit what's deployed. The contract-review skill isn't six slightly different copies floating around. It's one official skill, managed centrally, the same for everyone.
This is the model that matches how a regulated team, a legal department, an HR function, actually needs to work. The official playbook is provisioned by someone accountable for it, not improvised account by account. When you think about deploying a skill that carries real standards, admin provisioning is the path you want.
Admin provisioning: top-down rollout
The first way a skill becomes a team asset is an administrator pushing it out. This is for skills the whole organization, or a whole department, should run.
Organization-wide skill management is a feature of the Claude Team and Enterprise plans. On those plans, an administrator can upload a skill through the organization settings. Once they do, that skill becomes available to everyone in the organization. People find it in their Claude settings, under Customize, then Skills. They don't have to hunt for it or install anything; the admin's upload provisioned it to everyone.
Two control points matter here, and they're the reason this is the safe default for important skills.
The admin gate. On Team and Enterprise plans, an administrator enables Skills for the organization before anyone can use them at all. Skills are not just on by default. Someone with authority turns the feature on, and that same someone controls what gets pushed out.
Central control. Because provisioning runs through the admin, the organization has one place to manage skills: push them out, restrict them, and audit what's deployed. The contract-review skill isn't six slightly different copies floating around. It's one official skill, managed centrally, the same for everyone.
This is the model that matches how a regulated team, a legal department, an HR function, actually needs to work. The official playbook is provisioned by someone accountable for it, not improvised account by account. When you think about deploying a skill that carries real standards, admin provisioning is the path you want.