← use cases · registry
Sharing a curated skill set across a team
Publish skills to a registry and let your whole team install a consistent, versioned set.
Who it's for
Teams that want everyone to have the same high-quality completions for their internal and third-party tools.
The problem
Everyone re-generating skills locally means inconsistent quality and duplicated effort. Knowledge about how to drive a tool should be a shared, versioned artefact.
How skillterm does it
- 1
Validate a skill directory with skillterm publish --dry-run, then publish it to the registry.
- 2
Teammates install by name (skillterm install stripe), by version (name@version), or from GitHub (gh:user/repo).
- 3
Project skills in ./.skillterm/skills/ override user and system skills, so a repo can pin its own set.
- 4
skillterm search finds skills locally and remotely; skillterm update keeps them current.
publish and install
$ skillterm publish ./skills/internal-cli --dry-run$ skillterm publish ./skills/internal-cli# teammate:$ skillterm install internal-cli
The outcome
Skills become shareable units of knowledge — install once, and the whole team drives tools the same way.