Sharing skills across your team

The single most useful thing a team can do with skills is stop distributing them by hand.

Instead, keep a curated cache — your org's vetted set of skills — and let members sync to it. The model that holds up in practice:

1. The org cache is the source of truth. Skills are promoted into it deliberately.
2. Updates are pending, not automatic. Nothing changes under someone mid-task; they pull when they're ready.
3. Local edits fork, not clobber. If you tweak a synced skill, it's marked "diverged" rather than silently overwritten.

The same data that powers syncing also powers safety. Because every client reports what it has installed, you can answer "who's on code-reviewer@1.2.0 right now?" — and push a warning to exactly those people if a version turns out to be compromised. That retroactive recall is worth more than any install-time gate.

Start small:

npx @skst/skill add your-org/code-reviewer
npx @skst/skill update          # pull the current versions

Curate one cache, point your team at it, and the drift problem quietly disappears.