How to roll out a skill to your whole team

Who has to do it

• Claude: an Owner or Primary Owner. The role labeled Admin can't open the Plugins and skills page.
• ChatGPT: a workspace admin, in the Admin console under Plugins.

Pick the right setting

Both tools let you decide whether people get a skill automatically or have to install it.

• Claude: Required (always on), Installed by default (on, can be turned off), Available (people install it themselves) or Not available.
• ChatGPT: Installed, Available or Disabled.

If you want the whole team using it, choose Required or Installed by default in Claude and Installed in ChatGPT. "Available" mostly means nobody uses it.

Give each department only its own skills

The more skills everyone has installed, the more often the AI picks the wrong one. On Claude Enterprise you can set availability per group. On ChatGPT Enterprise and Edu you can set it per role. On Claude Team and ChatGPT Business, settings apply to everyone, so each skill's description has to make clear which job it's for.

Updating it later

Skills synced from GitHub update when the repository changes: Claude picks it up within about 30 minutes, and ChatGPT on its daily sync or when an admin presses Sync now. Skills uploaded by hand have to be uploaded again. Either way, change the master copy, not each person's setup.

Tell people what changed

People won't go looking for a new skill. Tell the team in a sentence what it does and give them two example requests to try. They don't need to name the skill; if the description is good, the AI will choose it.

See whether it's used

Claude's Plugins and skills inventory shows how many people used each item in the last 30 days, and each item's page shows how often. ChatGPT's admin Skills page shows invocations for the last 30 days, where available. If a skill isn't used, the description is usually the problem (see why skills don't trigger).