Short answer
Claude skills admin settings are the owner controls that install skills for your whole organization and decide what staff can add on their own. At Strategized.ai I run this pass before the second seat is added, so you can decide which skills every person gets and who is allowed to change that list.
Here’s the setup I usually walk into. The owner turned on skills, uploaded one good proposal skill and moved on. A few months later, staff have built their own versions. Two of them do the same job. Nobody knows which one the company stands behind.
This isn’t about writing better skills. It’s about who controls the list.
| Key fact | What Anthropic says | Source |
|---|---|---|
| Who gets organization-wide skills | Team and Enterprise plans, and the comparison table lists organization wide skills deployment for Team | Anthropic’s skills admin guide and Anthropic’s pricing page |
| What has to be on first | Cloud code execution and file creation, plus Skills, because skills require code execution to function | Anthropic’s skills admin guide |
| Provisioned skills | Enabled by default for everyone, and members can toggle one off | Anthropic’s skills admin guide |
| Adding and removing them | Only owners can add or remove organization-wide skills | Anthropic’s skills admin guide |
| Personal skill uploads | Can be turned off with User-created skills | Anthropic’s skills admin guide |
| Publishing by staff | Set to Requires review, Open or Off | Anthropic’s skills admin guide |
Install Once: Provision Claude Organization Skills Before the Second Seat
When you upload a skill through organization settings, it becomes available to everyone in your organization, and individual users no longer need to upload the same skill themselves (Anthropic’s skills admin guide). Whatever you provision on day one is what every new hire opens.
Two rules shape the decision. Owner-provisioned skills are on for everyone by default, though a member can switch one off for themselves. And only owners can add or remove them, so the company list stays in your hands.
In my consulting work, the first skills I provision are the ones that describe the business: who you serve, how you write, how you price a job. Those belong to the company, not to whoever wrote them first.

The click-by-click version lives on CoworkStrategy.com, in the guide to provisioning one playbook to every seat. Not sure which skills belong at the company level? Book a short call with Strategized.ai and I’ll sort the list with you.
The Claude Skills Admin Settings That Decide What Staff Can Add
Two switches answer the staff question. The first is User-created skills. By default, members can create their own skills and upload skill files. Turn it off and they can’t, while the skills you provisioned and Anthropic’s built-in skills stay available (Anthropic’s skills admin guide).
The second is Publishing, which decides whether a member can add a skill to the organization library:
- Requires review: members submit, and an owner must approve each one before it’s published.
- Open: submissions go straight to the library for everyone to install, with no review.
- Off: members don’t see the Publish to org button. Owners can still add skills directly.
On a Team plan, Publishing starts on Open unless Share with organization was already off. Most owners I talk to have never looked, so the default is making the call for them.

Pick One of Three Policies for Claude Skills for Teams
Pick the setting that matches how far you trust work to travel without you.
- Locked: User-created skills off, Publishing off. Staff use only what you provision. It fits client-confidential or regulated work.
- Reviewed: User-created skills on, Publishing set to Requires review. Staff experiment, and nothing reaches the whole company until an owner approves it. This is my default.
- Open: both on, Publishing Open. It fits a handful of experienced people who already agree on how the work gets done.
Review buys you one more lever. When you approve an item, you choose how it’s offered: Available to install, Installed by default, Not available, or Required (Anthropic’s skills admin guide). That’s the real answer to what staff can add. They can propose anything. You decide what lands on every desk.

When One List for Everyone Stops Working
A single company list works until departments disagree. Marketing doesn’t need the month-end close skill. Enterprise plans can give skills to only some users by bundling them into a plugin and assigning that plugin to a group (Anthropic’s skills admin guide).
That’s where a custom plugin earns its keep. My developers on staff build custom Claude plugins and keep them in a private plugin library, so each team gets its own set. Configuration is included in a Claude rollout for teams, and custom code is scoped separately.
I also pair this pass with a shared business profile project.
Prefer to watch? This short shows how one skill becomes something the whole team reuses.
If you’re a solo owner on one seat, none of this changes much. A setup call on CoworkConsultant.com is the better first step.
Michael’s take
The defaults aren’t wrong. They’re built for a company that hasn’t decided anything yet. Leave them alone and your skill library becomes a record of whoever was busiest, not how you run the business. I’d rather an owner spend one sitting on this before the second seat than untangle duplicate skills later. You own the list either way. The question is whether you chose it.
Your Settings Pass Before the Second Seat

Run this once, in order:
- Confirm code execution and Skills are both on.
- Provision the skills that describe your business, as an owner.
- Choose Locked, Reviewed or Open for User-created skills and Publishing.
- Decide which approved items are Required and which are only Available to install.
- Tell staff the rule: share to test, publish to roll out.
Want a second opinion before you invite the team? Book a short call with Strategized.ai. You’ll leave with a settings policy for your team and a clear view of whether a custom plugin is worth building.
Frequently Asked Questions
Who can add Claude organization skills for the whole company?
Only owners. Strategized.ai points clients to Anthropic’s note that only owners can add or remove organization-wide skills, while members can toggle a provisioned skill off for themselves (skills admin guide).
Can staff turn off a skill after you provision Claude skills for everyone?
Yes, for their own use. Strategized.ai confirms owner-provisioned skills are enabled by default for everyone, but each user can toggle individual skills off. They can’t delete them (skills admin guide).
Can Claude skills admin settings stop staff uploading their own skills?
Yes. At Strategized.ai I turn off User-created skills for locked-down teams. Users then can’t create skills or upload skill files, and provisioned and built-in skills stay available (skills admin guide).
Can I limit Claude skills for teams to one department?
On Enterprise, yes. Strategized.ai builds this as a plugin: Anthropic lets Enterprise plans bundle skills into a plugin and assign it to a group, so only that group sees them (skills admin guide).
