Your Claude skills library is Customize, then Skills: every skill you've added, uploaded or been given is listed there with an on and off toggle. On Team and Enterprise plans, as of October 2026, it splits into three sections, Personal skills, Shared with you and Organization skills, and the same library also loads in Claude Code and the Microsoft 365 add-ins.
Skills are only useful if people can find them and trust what's switched on. This page is the navigation view: where everything sits, who can change what, and where your library follows you once it's set up.
Where to find your library
Open Customize in the left sidebar, then Skills. The list shows Anthropic's own skills, any custom skills you've uploaded, when each one was enabled or uploaded, and a short description of what it does. Each skill has a toggle; a disabled skill isn't available to Claude at all.
If the Skills section is missing or greyed out, code execution is off. On Free, Pro and Max you fix that in Settings, then Capabilities. On Team and Enterprise it's an organisation setting in Organization settings, then Plugins and skills, in the Policy tab. To delete a custom skill, open it, switch it off with the toggle in the top right, then use the three-dot menu and choose Delete. You can bring it back later by uploading the file again.
The three sections on Team and Enterprise
| Section | What's in it | Who can change it |
|---|---|---|
| Personal skills | Skills you created or uploaded yourself | You |
| Shared with you | Skills a colleague shared with you directly; they stay off until you turn them on | The colleague who owns it; you can enable, disable or delete your copy |
| Organization skills | Skills published to your organisation and skills an owner provisioned; you install these from the directory | Owners and reviewers; you can disable a provisioned skill but not delete it |
| Anthropic skills | The built-in Excel, Word, PowerPoint and PDF skills | Anthropic; you can only toggle them |
Shared skills are view-only for the people who receive them. They can use the skill, but not edit it, and when the owner updates it, everyone gets the new version the next time they use it. Access disappears automatically if someone leaves the organisation.
Adding skills from the directory
- Go to Customize, then Skills, and click the plus button.
- Choose Browse skills to open the directory. On Team and Enterprise, the Your organization tab lists skills available to everyone in the company.
- Click Add on the skill you want. It appears in your list, enabled by default.
- Toggle it off if you change your mind. It stays in the directory so you can turn it on again later.
- If you want to change how it works, download a copy, edit it, and upload it as your own, because directory skills are view-only.
Skills shared with you directly don't show up in the directory at all; they go straight into your list. And if you add a plugin, its skills come with it, because each plugin bundles skills, connectors and sub-agents into one package. My guides to Claude plugins and Claude connectors cover those other two pieces.
Sharing, publishing and provisioning
These three words sound alike and do very different things. The Help Center puts the first two neatly: sharing gives a skill to specific people or groups and you keep control of it; publishing hands it to your organisation.
- Share: open Customize, then Skills, find your skill, click the three-dot menu and choose Share. Pick specific people, or on Enterprise a group. It lands greyed out in their list until they enable it, with your name as the owner.
- Publish: open the skill and click Publish to org. If your organisation requires review, you propose how it's offered (Available to install, Installed by default or Required) and a reviewer approves it. You'll see its status as pending, changes requested or published. Once published, the organisation manages it, and it stays even if you leave. You can't publish a skill shared with you, Anthropic's built-in skills, or one you installed from the library.
- Provision: owners go to Organization settings, then Plugins and skills, click Add and upload or create a skill. It appears for everyone straight away, enabled by default, and people can toggle it off. On Enterprise, owners can limit skills to a group by bundling them in a plugin assigned to that group, for example a set of marketing skills for the marketing team.
Owners can also turn off User-created skills in the Policy tab. When they do, people can't create or upload their own, but provisioned skills and Anthropic's built-in skills stay available. On Enterprise, skill scanning can check uploaded skills and plugins for malicious content; most scans finish in about one to two minutes, and a blocked skill can't be used until it's fixed and uploaded again.
Where else your library shows up
The library isn't just for the chat window. As of October 2026:
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
- Claude Code: skills you've enabled, and skills your owner provisioned, load in the terminal when you sign in with the same Claude account, on version 2.1.273 or later. Run /skills to see them under claude.ai sync. They sync when a session starts and then check for changes about every 10 minutes. The sync is one-way and never changes your Claude account. It doesn't run if Claude Code uses an API key or a cloud provider such as Amazon Bedrock.
- Microsoft 365 add-ins: enabled skills also work in the Claude for Excel, PowerPoint, Word and Outlook add-ins. Type a slash in the sidebar to see them, or describe the task and let Claude pick.
- The API: this one doesn't follow you. The Platform docs say a skill uploaded to claude.ai has to be uploaded to the API separately.
How I'd run a skills library
I'd keep the library small and name each skill by the job it does, so anyone scanning the list knows what it's for. Skip turning on every skill you come across. That part's my opinion rather than anything Anthropic says: each extra skill is one more option Claude has to choose between, and a short list is easier for a team to trust. If you're on a Team plan, agree who owns each published skill, and review the list every quarter. Getting a whole team comfortable with this is easier with some structure, which is why Claude training for teams is where I'd start once the library's in place.
If you're setting up a shared skills library for your team and want it organised from day one, that's the kind of AI enablement I help with. I run AI training and workshops for teams, and help businesses with AI enablement and workflow automation, so the busywork runs itself and people get time back. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.
Frequently asked questions
Where is my Claude skills library?
In Customize, then Skills. It lists Anthropic skills, your custom skills, when each was enabled or uploaded, and a short description, with a toggle for each.
What does Shared with you mean in Claude skills?
On Team and Enterprise plans, it's the section for skills colleagues shared with you directly. They stay off until you turn them on, and you can use them but not edit them.
What's the difference between sharing and publishing a Claude skill?
Sharing gives a skill to specific people or groups while you keep control. Publishing hands it to your organisation's library, often after an owner reviews it.
Do my Claude skills work in Claude Code?
Yes, on Claude Code version 2.1.273 or later when signed in with the same Claude account. Run /skills to see them. They don't sync with an API key or Amazon Bedrock.
Can I delete an organisation skill from my list?
You can disable a skill your owner provisioned, but you can't fully delete it. Only an organisation owner can remove it from the directory.
