Teaching Everyone at Once
A skill written for your own agent teaches one assistant. Committed into a public repo, it teaches every agent that opens the folder. Two skills from the sandbox run just made that jump.
A correction you write down teaches your agent. A correction you ship teaches everyone’s.
I have written before about teaching it once: the discipline of making every correction leave something behind, so a preference becomes a memory, a rule becomes standing configuration, a recurring job becomes a small skill. All of that lives in your own setup, and it compounds, but only for you. There is a natural next step that took me a while to see: the configuration can ship with the code.
When I ran the Operations Blueprint on a shop that does not exist, the run left behind two procedures that had actually worked. One is for getting a shop’s messy spreadsheets into a relational schema without losing a row. The other is for building the first working slice of an operations system in the right order. Both sat in the sandbox’s lessons folder under a rule I set for myself: they do not become real skills until a second, different shop proves they hold.
They now ship inside the open-source repo as Claude Code skills, at v0.1, with that rule printed on them: validated on one archetype so far, a second archetype is the gate for v1. The ingestion skill carries the line I most wanted to keep: never silently drop an unmappable row, because “a dropped row is a silent hole in a price.” The slice skill ends with the ordering rule the whole build hangs on: “Slice one earns trust; the rest of the build spends it.”
Here is the part worth taking with you. A skill in your home configuration improves your sessions. The same skill committed next to the code changes who it teaches: any agent that anyone points at the repo now starts with the lessons the sandbox paid for. It is the expertise-in-each-folder pattern, running in public. The repo’s source folders carry their own context files stating the invariants a change must preserve, and the skills carry the procedures, so the next builder’s agent does not relearn any of it from scratch.
If you keep a private library of corrections, look through it for the two or three that would survive contact with a stranger’s project. Those are not configuration anymore. They are the most useful thing you could publish. And if you try these two and they break on your shop’s data, that is not a failure of the idea; that is the second archetype the v1 gate is waiting for.