FREE GUIDE · FOR AI OPERATORS

Ship Your Own Skills as a Plugin

Everyone on your team has their own copy of the same skill, and the copies drift without telling you. Here is the one-source fix, and it goes up in an evening: what the shared folder has to look like, the one command that publishes a change, the number that decides whether anyone ever sees it, and the setup order for the second machine.

What you'll learn

What a shared skills folder looks like once it is a plugin, and why a copy on each machine is not one

The five things one publishing command has to do in order, and the three times it should refuse

Why a published change can reach nobody, with no error anywhere, and the single number behind it

How an update lands on a teammate's machine without anyone typing anything, and four checks when it does not

For Operators who already use Claude Code daily and have written their own skills · Small teams running the same skills across more than one machine · Anyone keeping copies of the same instructions matched by hand

The copy that kept working while it was wrong

When copies of the same skill drift apart, the instinct is to build something that watches them and warns you. That was our first move and it was the wrong one. A watcher treats the duplicate as permanent, so now you maintain both copies and the watcher too. Delete the duplicate and there is nothing left to watch. In our experience the expensive part is that nothing visibly breaks: the outdated copy answers just as confidently as the current one, and you cannot tell from the answer which one got read.

“A watcher for drift is a standing promise to maintain both copies forever, where deleting one ends the job.”

From the opening, where the first thing we built turned out to be the wrong fix.

Want this running across the whole business?

We build it with you, on your systems, and your team runs it.

Get Started →