Teams

Teams are the organizational unit in the Skills Registry. Each team has its own scope (namespace) for publishing skills.

Creating a Team#

You can create a team through the web UI at /teams or via the API (POST /api/v1/teams).

The team slug is used as the scope namespace for all skills published by the team. Slug requirements:

Lowercase alphanumeric characters and hyphens only
Must be between 2 and 64 characters
Must start with a letter or number

Roles#

Each team member is assigned one of four roles. Roles are hierarchical — each role includes all permissions of the roles below it.

Role	Permissions
owner	Full control. Delete team, transfer ownership, delete skills. All admin permissions.
admin	Manage members (invite, remove, change roles except owner). Update team settings, manage channels, yank versions. All member permissions.
member	Push versions, create skills in team scope, star skills, submit reviews. All viewer permissions.
viewer	Read team skills, including skills with team-level visibility.

Warning

Only owners can promote another member to owner or delete the team. This action cannot be undone, so assign the owner role carefully.

Managing Members#

Team admins and owners can manage the team roster through the web UI or the API.

Invite a member:

Members can be invited through the web UI team settings page or via the API (POST /api/v1/teams/:slug/members). The default role for new invites is member.

Change a member's role:

Use the web UI team settings page or the API to update a member's role. Admins can change roles up to their own level (but cannot promote to owner).

Remove a member:

Use the web UI team settings page or the API to remove a member from the team. Removing a member revokes their access to team-visibility skills immediately.

Info

When you create a team, you automatically become the owner. Every team must have at least one owner at all times.

Team Scopes#

Skills are published under a team's scope, which matches the team slug. For example, a team with slug backend publishes skills at @backend/skill-name.

All team members with the member role or higher can publish skills under the team scope. The scope is exclusive to the team — no other team can publish skills under another team's scope.

Tip

Choose a short, memorable team slug since it becomes the prefix for all your published skills. Team slugs cannot be changed after creation.