Skip to main content

Sharing skills with your team

A skill on your laptop helps you. A published skill means the team runs the same method, instead of six slightly different prompts.

Scheduled tasks do not share across computers. Skills do. If the whole team needs the Monday brief, share the skill, and let each person attach their own task. Or one person owns the task and posts the result. Don't expect the task itself to appear on everyone else's machine.

How to access it​

Publishing to the organisation needs Team or Enterprise. Pro can still share a skill file by sending it. Check the current price at claude.com/pricing.

The switch people miss: uploading a file is not the same as publishing it. A file in your folder is yours. Publish is what puts it in the org library for everyone else.

Steps​

  1. Get the skill working on your account first. Run it twice. Fix it. Don't publish a first draft.
  2. Open Customize > Skills.
  3. Publish it to the organisation, or send an email invite, or upload the skill file.
  1. Tell people the plain-English ask, and the /name if they need to force it. A skill with no instruction gets ignored.
  2. Put a copy of the skill folder in the shared company drive, with a date in the name or a one-line changelog. The app is where people run it. The folder is where you can see what changed.

Who owns it​

One owner per skill. They take corrections. Everyone else suggests. If three people edit the shipping-note skill, you get three versions and nobody knows which one ran.

Name skills for the job, not the author. /shipping-note, not /alex-email-v7.

When you change the steps, say what changed in the changelog. "March: don't promise a delivery date that isn't on the order."

Installing someone else's skill​

Read it before you run it. Open SKILL.md. Check what it can read, what it writes, and whether it tells Claude to send, delete, or browse.

A skill is instructions. It can tell Claude to do something you wouldn't. If you didn't read it, you don't know.

Read this skill and tell me, in plain language:
- what it will try to do
- what it needs access to
- whether it sends, deletes, or changes files
Don't install it yet.

Worked example. A small team at a consumer brand published one "weekly update" skill after the session. The owner was the ops lead. Marketing used it for the internal note, not for customer emails. When the format changed, the ops lead edited the skill and wrote one line in the shared folder. People didn't keep private copies.

Pro tips​

  • Share three skills, not thirty. The ones you actually repeated.
  • Personal tone stays in your folder. Shared skills should call the company voice, or tell the person to use their own tone file.
  • If a teammate's result is wrong, fix the shared skill. A private tweak means you're back to six versions.

Limits​

Enterprise admin controls may mean you can't publish without an owner. If Publish isn't there, ask the Team owner. Don't work around it with a personal account full of company files.

An email invite is easy to miss. If someone says they don't have the skill, check Customize > Skills on their login, not yours.

Tasks still don't travel. Sharing the skill does not put Tuesday's scheduled run on their laptop.

Where to start in 30 minutes​

  1. Pick the one skill from the session that someone else will need.
  2. Read it. Remove anything that only makes sense for you.
  3. Publish it, or upload it, on the Team account.
  4. Send the /name and one example input to the people who should use it.
  5. Ask one of them to run it while you're watching. Fix what confused them.