Skillsets
Curated, cross-registry bundles that install as a unit, carry per-item config, and can be org defaults offered during bootstrap.
A skillset is a named, curated bundle of skills that installs as a single
unit. Its reference lives under the owner's skillsets namespace:
@studio/skillsets/new-client-projectWhere a registry is a single collection you publish into, a skillset curates across registries — it is a hand-picked list, not a namespace of its own.
What's inside a skillset
Skillset items can be:
- Individual skills, each with its own version range or dist-tag.
- Whole registries, each with its own follow / exclude / version-policy config — the same knobs as a registry subscription.
Because items can point at different registries, one skillset can assemble exactly the skills a team needs regardless of where they live.
Installing a skillset
Install a skillset like any other reference:
skillhub install @studio/skillsets/new-client-projectResolution happens server-side — the registry expands the skillset into its concrete skills and applies each item's config.
Org defaults and onboarding
Organizations can mark skillsets as defaults. When someone bootstraps a
project, skillhub init offers those default skillsets so a new project starts
with the team's standard skills already lined up. You can also name one directly
during bootstrap:
skillhub init --skillset @studio/skillsets/new-client-projectWhy skillsets, not just a registry install
A skillset centralizes the install configuration once for a whole team and carries org-default status for onboarding. That's what sets it apart from a plain registry install: instead of every developer remembering which skills and what version policy to use, the skillset encodes that decision once and offers it automatically.