Scattered SKILL.md files drift. A versioned, shared repo is the difference between "it worked on my machine" and shared infrastructure.
Most teams start the same way: a few SKILL.md files copied between machines, pasted into
Slack, half-remembered. It works — until it doesn't. One person tweaks the review skill,
another never gets the update, and now your agents disagree about your own conventions.
A skill repo fixes this the way a package registry fixed dependencies:
- One source of truth. The current version lives in one place; everyone pulls it.
- Versioning.
add owner/skill@3 pins a known-good version; upgrades are deliberate.
- Provenance + checks. Every publish runs safety and quality checks, attached to the
version, so you know what you're installing before an agent runs it.
- Recall. If a skill turns out to be bad, you can see exactly who has it and warn them.
The convenient path becomes the safe path: pull from the shared repo and you're current,
checked, and consistent by default — not because someone told you to, but because it's easier.
npx @skst/skill add your-org/code-reviewer
