Skip to main content
The workspace a skill belongs to decides who can find, use, and change it. Use this guide before you publish a skill, or when teammates cannot find one they need. To create workspaces or manage members, see Manage workspaces instead.

Before you begin

Before you start, make sure you have:
  • A skill to publish: a skill folder with SKILL.md, or an existing skill in your personal workspace.
  • Contributor access: the Builder or Workspace admin role in the shared workspace you plan to use. Viewers cannot publish.
1

Choose scope

Match the skill to the people who use and maintain it.
  • Personal workspace: you are still trying the skill, or it only supports your own work. Only you can see it.
  • Existing shared workspace: the same team will use and maintain the skill.
  • New child workspace: the team needs its own admin, member list, or access boundary. Ask a workspace admin to create it.
2

Confirm your workspace role

You need Builder or Workspace admin to publish. If you are not sure of your role, ask a workspace admin. They can see every member’s role on Access in the workspace’s settings (More actions → Workspace settings on its home) and change it there.If the workspace shows Join workspace, joining adds you as a Builder.
3

Publish to your chosen workspace

Publish with the method that fits where the skill’s source lives: desktop bulk upload, the CLI, or GitHub SkillSync. Each method writes the skill to one workspace. See Publish and version a skill to choose one.
4

Verify skill visibility

In the workspace, open Skills in the sidebar and use Search skills to find the skill by name. The list shows only this workspace’s skills.When shared discovery matters, ask a teammate with the role you expect readers to have to search for it. Do not test with an account that has more access than the intended reader.

Troubleshooting

If the skill does not appear, the selected workspace or your role is usually the cause. See Workspace access errors.

Next steps