product
How to share Claude skills with non-technical colleagues
A practical guide to sharing Claude skills with colleagues who never open a terminal: built-in sharing options, a publishing flow, common fixes, and when a central role fits better.
- #skills
- #claude
- #agent-plugins
- #roles
- #governance
How do you share Claude skills with a non-technical colleague?
On a Claude Team or Enterprise plan, upload the skill, then share it with that person or publish it to your organisation’s library. Your colleague switches it on once in Customize > Skills and then asks Claude for the task in plain words. No terminal, no ZIP file and no Git repository are involved on their side.
That route has limits. It works only inside one Claude organisation, and individual plans (Free, Pro and Max) cannot share skills at all. It also does nothing for a colleague who works in ChatGPT or Microsoft Copilot.
Which ways of sharing Claude skills exist today?
There are six ways to get a Claude skill to someone else, and three of them suit a non-technical colleague: sharing with people, sharing with a group, and publishing to the organisation library. The other three (owner provisioning, a Claude Code plugin marketplace and the Skills API) need an owner or a developer.
A skill is a folder with a SKILL.md file (instructions plus a name and a description) and optional scripts or reference files. Anthropic published the format as an open standard, Agent Skills, in December 2025, so the same folder can also load in other assistants.
| Method | Plan | Colleague effort | Best for |
|---|---|---|---|
| Share with specific people | Team, Enterprise | One toggle | A pilot with a few people |
| Share with a group | Enterprise | One toggle | One department |
| Publish to the organisation library | Team, Enterprise | Install, or nothing if “Installed by default” | Company-wide use |
| Owner-provisioned skill | Team, Enterprise | None | Mandatory standards |
| Claude Code plugin marketplace | Any Claude Code user | Terminal commands | Developers |
| Skills API | API | None, built into an app | Internal tools |
“Claude plugins” and “Claude Code plugins” often come up in the same search. A plugin bundles skills with other parts, such as MCP servers and commands (MCP, the Model Context Protocol, is the open standard assistants use to call external tools), and a plugin marketplace is a catalogue developers install from with terminal commands. It suits engineering teams, not a sales assistant or a site manager.
What limits apply before you start?
The Claude Help Center (2026) lists four conditions worth checking first:
- Plan gate. Users on individual plans can upload skills for themselves but cannot share or publish them.
- Code execution must be on. Skills do not appear unless “Code execution and file creation” is enabled for the organisation and for the user.
- Shared skills are view-only. Recipients can run a shared skill but not edit it.
- Group targeting is Enterprise-only. On Team, a skill goes to named people or to the whole organisation.
How do you publish a skill a colleague can find and run?
Check the organisation policy, write the description in your colleague’s words, upload the skill, test it as a beginner would, then share or publish it. On a Team or Enterprise plan this is a short task, plus review time if your organisation requires approval. Menu names follow the Claude Help Center as of November 2026.
- Ask an owner to check the policy. In Organization settings > Plugins & skills, on the Policy tab, “Skills” and code execution must be on, “Skill sharing” must be on to share, and “Publishing” must be Open or Requires review to publish (Claude Help Center, 2026).
- Write the description for your colleague. Claude decides when to use a skill from its description. Use the words your colleague will type, for example “site report” rather than “DSR generator”.
- Upload the skill. In Customize > Skills, click +, then + Create skill, then Upload a skill, and select the ZIP file. The folder name must match the skill name.
- Test it as a beginner would. Open a new chat and type the plain request without naming the skill. If Claude does not pick it up, sharpen the description.
- Share or publish. Each custom skill has a … menu with two entries, Share and Publish to org. For a pilot, choose Share, then Specific people or A group (Enterprise). For everyone, choose Publish to org.
- Choose how it is offered. The publishing dialog offers Available to install, Installed by default and Required, plus a field for release notes. For non-technical users, “Installed by default” removes the install step.
- Wait for review if needed. Under Requires review, an owner or reviewer approves the skill in the Requests tab.
- Tell your colleague what to type. Send one example request, not an explanation of skills.
A message along these lines works (sample text):
Hi Anna, Claude can now write the weekly site report for you. Open Claude and type: “Write this week’s site report for Lausanne Nord from these notes”, then attach your notes.
Updating later. Publish again after each edit. The new version goes through the same review, and users stay on the approved version until then.
What does your colleague see after you share a skill?
Your colleague switches the skill on once, then asks for the task in normal words. Where the skill appears depends on how you shared it, as the Claude Help Center (2026) describes. In every case they can run the skill but cannot edit it, which keeps one version in circulation.
| How you shared it | Where it appears | What they do once |
|---|---|---|
| Specific people or a group | Customize > Skills, section Shared with you | Turn the toggle on |
| Published, “Available to install” | The Your organization tab of the directory | Click Install |
| Published, “Installed by default” | Organization skills, already on | Nothing |
A directly shared skill arrives switched off: in Shared with you, its toggle is greyed out, with your name as owner, until the colleague turns it on. After that, they type a request such as “Draft the credit note for order 4471” (a sample order number) and Claude loads the skill when the request matches its description.
What if the colleague uses ChatGPT or Copilot?
Claude sharing does not reach other assistants, so you maintain one copy per tool or serve the skill from a central place. Because SKILL.md is an open format, the same folder can be uploaded elsewhere, but each assistant has its own sharing and administration rules.
- ChatGPT (Business, Enterprise, Edu): upload under Skills, then share with people or groups or publish to the workspace library. According to the OpenAI Help Center (2026), OpenAI planned to switch skills on by default from 23 July 2026 for Enterprise workspaces that did not opt out.
- Microsoft Copilot Cowork: skills are packed into a Microsoft 365 app package that an admin uploads, as described in the Microsoft Learn guide to Cowork plugins updated in October 2026.
Three copies mean three places to update, three review flows and three sets of logs. As the library grows, copies drift apart and loose SKILL.md files end up in personal folders, which is how unmanaged skill files become shadow AI.
Why can’t a colleague see or run a shared skill?
Most reports of a skill that “doesn’t work” come from one of four switches: the organisation policy, the colleague’s own toggle, their permissions, or the skill’s description. Check them in that order. The fixes follow the Claude Help Center guide for admins (2026).
| What the colleague says | Likely cause | Who fixes it |
|---|---|---|
| ”I don’t see a Skills section” | Code execution or Skills is off in the Policy tab or in their settings | Owner, then colleague |
| ”The skill is greyed out” | Shared skills arrive switched off | Colleague |
| ”Claude ignores the skill” | The description does not match how they ask | You |
| ”I can’t find it in the directory” | Not yet approved, or the security scan failed | Owner or reviewer |
| ”Permission denied” when the skill calls a tool | No authorised connector, or no access to the data | Colleague, then IT |
The last row matters most. A skill does not carry your access rights. It runs with the colleague’s own connectors and permissions, which is the safe behaviour and the basis of least-privilege access for AI agents. Test with an account that has the same rights as the intended user, not with an admin account.
When is a central role a better fit than built-in sharing?
Built-in Claude sharing is the better fit when everyone uses Claude and you have a handful of skills. A central approach pays off when skills must work in more than one assistant, or when each team needs a named owner, versions and scoped access to tools across assistants.
A skill alone carries the method. It becomes useful in production when it travels with the MCP tools that reach the team’s systems. This is how skills and MCP tools work together.
skilder packages that bundle as a role: a team’s skills, its scoped MCP tools from an internal, curated registry, its access rights and, where useful, an app interface. Each role is configured from a blueprint, a starting template the team adapts to its own method. The wider ecosystem calls such bundles plugins, as the comparison of agent plugins and skilder roles explains.
The business team that knows the job owns and maintains its role, for example a “site manager” role. IT governs access, permissions, hosting and audit. Colleagues use the same role from Claude, ChatGPT, Copilot Studio, VS Code or any MCP-compatible agent:
- One source, many assistants. The assistant connects once over MCP with OAuth and receives the current version of each role the user may use.
- Versioning and rollback. Every change is versioned and can be rolled back.
- Own permissions only. Tools run with the requester’s own permissions, so a role never grants more access than the person has.
- Access and audit. Enterprise SSO, role-based access control and workspace isolation; each run leaves an execution trace attributed to the user, and the audit log can be exported.
- Data. Hosting in Switzerland (Infomaniak) and the European Union, on-premise on request, zero retention at the model providers.
If your team is weighing which skills to centralise first, a free 30-minute exchange with an expert helps sort the candidates. A first role can be set up in free self-service, and the skilder deployment service puts the first skills in production within two weeks when the calendar is tight.
Which option should your team choose?
For a pilot, share the skill with a few named people. For a company standard on Claude, publish it to the organisation library as “Installed by default”. When the same know-how must also reach colleagues in ChatGPT and Copilot, or when each team needs to own and version its skills, a central role avoids keeping three copies in step.
Takeaway: share the request your colleague should type, not the skill file, and give every shared skill an owner who knows the job.
To map your own skills to the right sharing route, book a free 30-minute exchange with an expert.
Frequently asked questions
Can I share a Claude skill with a colleague on a Pro plan?
No. Sharing and publishing skills need a Claude Team or Enterprise plan. On Free, Pro or Max, you can still send the skill as a ZIP file, and your colleague uploads it to their own account under Customize, then Skills. Their copy is independent: it does not receive your later edits, so you have to send each new version again and ask them to replace the old one.
Does my colleague need to install anything or use a terminal?
No. On Team and Enterprise plans, a skill shared with them appears in their skills list and they switch it on once with a toggle. A skill published to the organisation as Installed by default needs no action at all. Only the Claude Code plugin marketplace route requires terminal commands, which is why it suits developers rather than business colleagues.
Why can't my colleague edit the skill I shared?
Shared and published skills are view-only by design, so one approved version stays in circulation. Your colleague can download the skill, change their copy and upload it as their own, but that copy no longer receives your updates. For lasting changes, they send their suggestion to the skill author, who edits and republishes the shared version for everyone.
What happens to a shared skill when I leave the company?
Direct shares end when the owner or the recipient leaves the Claude organisation, according to the Claude Help Center (2026). Skills published to the organisation library stay available after the author leaves. Anything a team depends on every week should therefore be published to the library, with a named person in the team responsible for keeping it up to date.
Can the same skill work in Claude, ChatGPT and Copilot?
The file can, because Claude, ChatGPT and Microsoft Copilot Cowork all accept the Agent Skills format built around a SKILL.md file. Sharing, permissions and review do not carry over between them. You either maintain one copy per assistant, each with its own update and review flow, or serve the skill from one central place that every assistant connects to.
Does a shared skill give my colleague access to my data or tools?
No. A shared skill runs with your colleague's own account, connectors and permissions, never with yours. If they lack access to a system the skill uses, they see an error until IT grants that access through the usual channels. Test a skill with an account that has the same rights as the intended user before sharing it widely.
What is the difference between Claude skills and Claude plugins?
A Claude skill is a folder with SKILL.md instructions, plus optional scripts or files, that teaches Claude one task. A plugin bundles several parts, such as skills, MCP servers and commands, into one package that installs together. Claude Code plugins are distributed through marketplaces, which are catalogues hosted in Git repositories and installed with terminal commands.
Is there a Claude skills marketplace for companies?
For a company, the closest equivalent is the organisation's own skills directory on Team and Enterprise plans. Authors publish skills to it, owners or reviewers approve them, and members install them from the Your organization tab or receive them by default. Developer teams can also run a Claude Code plugin marketplace from a Git repository for plugins that bundle skills with tools.
Related articles
-
November 15, 2026
AI agent glossary: role, skill, MCP server and the terms around them
Plain definitions of the terms that come up when a company governs AI agents: role, blueprint, skill, SKILL.md, MCP, MCP server, connector, registry, context lake, execution trace and more.
-
November 10, 2026
How to turn an SOP into an AI skill employees can run in Claude, ChatGPT or Copilot
A step-by-step guide to rewriting a standard operating procedure as an AI skill: a SKILL.md template, a worked example, MCP tools, tests, versions and an owning team.
-
November 11, 2026
MCP gateway vs skills platform vs Copilot Studio: which one to start with
An MCP gateway governs tool access, Copilot Studio builds Microsoft 365 agents, and what buyers call a skills platform is really agent roles. What each one does, and which one to start with.