Spaces

Skills live in spaces — containers that control access and organisation within your org.

Default spaces

Every org starts with three spaces:

Space	Type	Purpose
General	Team	Shared space for the whole org. All members can see skills here.
Public	Public	Skills visible to anyone on the internet. Admins manage what's published here.
Personal	Personal	Your private workspace. Only you can see skills here.

Any org member can create a new team space:

sherpi spaces create engineering --name "Engineering"

Spaces have a slug (URL-safe identifier) and a display name.

Spaces can be open (any org member can join) or private (members must be added by an admin).

sherpi spaces edit engineering --visibility open
sherpi spaces edit engineering --visibility private

List members of a space:

sherpi spaces members engineering

Add or remove members:

sherpi spaces add engineering max@team.com
sherpi spaces remove engineering max@team.com

Change a member's role:

sherpi spaces role engineering max@team.com admin

Join an open space:

sherpi spaces join engineering

Leave a space:

sherpi spaces leave engineering

Each space inherits the org's auto-publish setting by default. Space admins can override it:

sherpi spaces edit engineering --auto-publish true
sherpi spaces edit engineering --auto-publish false

When auto-publish is on, skills go live immediately without admin review.

When you publish or install a skill, you can target a specific space:

sherpi skills publish my-skill --space engineering
sherpi skills install engineering/my-skill

If you don't specify a space, skills go to your default space (usually General).

Space admins can delete a space. Skills in the space are archived, not permanently deleted:

sherpi spaces delete old-space --force