Workspace Skills let admins make Skills available or mandatory for every user in the workspace. Instead of asking each person to find and install the right Skills, you set them up once and they are active for everyone automatically.
Before deploying a Skill, build it first. See Creating Skills for all three creation methods.
Two types of workspace deployment
Both options are configured from the Share dialog on the Skill itself. Open a Skill, click Share, and you will see a General access section (visible to admins only).
Workspace-shared Skills
Set General access to Workspace in the Share dialog. The Skill becomes visible to all workspace members. Users can discover it on the Skills page and choose to install it. Sharing does not force the Skill on anyone.
Workspace-mandated Skills
In the Share dialog, set General access to Workspace, then check Apply for all members. This makes the Skill active for every user automatically. Users cannot disable it. A lock icon indicates that a Skill is mandated.
The “Apply for all members” checkbox is only visible to admins.
Workspace-mandated Skills cannot be disabled by individual users. They are always active for everyone. Use this for guardrails and standards you need enforced consistently, such as compliance language or brand tone.
If users have to consciously navigate somewhere for something that should just always work, that is a sign it belongs in a mandated Skill.
Permissions
| Permission | Member | Editor | Admin |
|---|
| Create skills | Yes | Yes | Yes |
| Share skills with individual users and groups | Yes | Yes | Yes |
| Share skills with the entire workspace | No | No | Yes |
What to put in workspace Skills
Skills work best when the instructions capture something your team does repeatedly and needs to do consistently. A few examples:
- Tone of voice. Your brand guidelines applied to every output, for every user, without anyone having to think about it.
- Output formats. Status updates, meeting summaries, and project briefs all following the same structure across the team.
- Compliance language. Legal or regulatory requirements injected automatically into relevant outputs so they are never forgotten.
- Customer-facing standards. Support replies and proposals that match your style guide, consistently.
- Integration workflows. A “Client Email” Skill with your CRM integration attached so users get that capability without setting it up themselves. See Skills and Integrations.
For more examples with full instructions you can copy or adapt, see the Skills Guide.
What happens when you mandate a Skill
When a Skill is mandated:
- It becomes active for all workspace members immediately.
- Users cannot toggle it off.
- It appears with a lock icon in the Skills list.
- It counts toward the user’s active Skills (limit: 20 per user).
- If the workspace already has 8 mandated Skills, the action will fail. Remove one first.
Sharing vs. mandating
| Workspace-shared | Workspace-mandated |
|---|
| Visible to all members | Yes | Yes |
| Users must install it | Yes | No, auto-active |
| Users can disable it | Yes | No |
| Lock icon shown | No | Yes |
| Counts toward 8-Skill limit | No | Yes |
