Distribute and Maintain Skills Across a Team
Getting a skill onto one machine is easy. Keeping a team on the same version, and knowing when one has gone stale, is the actual work.
Pick the scope on purpose
Personal installation puts a skill under your home directory, where it applies to everything you do and nobody else has it. Project installation puts it inside a repository, where it applies to that codebase and arrives with every clone.
The rule that works: if it encodes how this codebase does things, it belongs in the repository. If it encodes how you work as a practitioner, it belongs in your home directory. Conventions travel with the code; judgement travels with the person.
Getting this wrong is quietly expensive in one direction. A repository convention installed personally means only you follow it, and you will assume everyone does because nobody hits the problems you have stopped hitting.
Version control is the distribution mechanism
For project skills there is nothing to build: commit the folder and distribution is solved. Everyone who clones gets the current version, changes arrive through review, and the history explains why a rule exists.
That review path matters more than it sounds. A skill is a set of instructions that will shape a lot of work, so a change to it deserves the same scrutiny as a change to a lint rule. Skills edited directly on individual machines diverge within weeks.
For skills shared across repositories, keep them in one repository of their own and let people install from it. Copying a folder between projects feels faster and guarantees that six versions exist, all slightly different, none obviously canonical.
5 more sections in this article
- Onboarding a new person
- Knowing when one has gone stale
- Ship the cases with the skill
- Handling disagreement
- Measuring whether it worked
This is Pro content
Get Agent Factory Pro - a one-time payment for lifetime access to full articles, complete build prompts, and everything new.
Use it
The parts of the library that put this article to work.
Published 14 August 2026. Last reviewed 17 August 2026. We re-read this library on a schedule and date every article, so you can see for yourself how current it is.