You finally got an agent working exactly how you wanted, and then you switched tools and it broke. That small, maddening moment is becoming one of the most expensive problems in knowledge work, and it is the second act of a problem that began with memory.
Open Brain was about memory leaving our heads. Notes, transcripts, Slack threads, calendars, meeting summaries, project histories. Huge parts of what we know had already moved into software. The trouble was that AI could not reliably use that memory, and when it could, the memory was trapped inside one company’s product. Open Brain made one claim: your memory should be yours. Whoever owns the memory owns the starting point, and the architecture itself was never the interesting part. If your context lives in one app, every new tool makes you start over and every better model arrives with a switching cost.
Open Skills is the same fight, one level up, and more urgent. Our skills are leaving our hands now too, and that should feel uncomfortable. For most of human history a skill lived in a person. You knew how to research, write, code, test, review work, and recover when something broke. You carried the standards, the shortcuts, the taste, and the checks that kept bad work from becoming real damage. AI is turning that into software. Your way of working can now become prompts, SKILL.md files, runbooks, scripts, MCP configs, permission boundaries, and agent workflows. The thing that used to live in your hands can now live in a harness.
That is one of the biggest opportunities in AI. It is also one of the biggest ownership fights. Because if your skills are going to live outside your hands, they should not belong to a rent-a-brain. Not to Claude because it shipped the best skill format this quarter, not to Codex because it gave you the best workbench, not to Cursor because the project started there, not to ChatGPT because the subscription was convenient. They should be yours. Visible, movable, inspectable, testable, and available wherever you work.
Today almost none of that is true. The prompt copies over. The intention copies over. The skill does not. So you rebuild it from memory, a teammate improves a different copy and never tells you, and your best workflow ends up stranded in a chat history nobody can find again. You are not short on intelligence or context. You are short on a way to carry the procedure itself.
That gap has a cost, and it compounds. Every tool switch becomes a rebuild. Every new hire starts from scratch. Every improvement risks dying as one person’s private habit. This is not a hobby problem. If agents are part of how you do your job, the skills you build with them are career capital, and right now most of that capital is rented back to you by whichever vendor’s tool you happened to build it in. Putting it back in your hands is one of the real practical projects of 2026, and it is bigger than any single file format.
Here’s what’s inside:
Open Skills, the library. A public set of agent skills and runbooks you can install today, built on one rule: the way you work should be yours, not rented back to you.
The debt you didn’t know you were carrying. The four ways this breakage shows up at work, and the name for what you keep paying down.
Prompt, memory, skill. Three things people collapse into one, and why only one of them survives a model change.
The work package. A checklist that separates a skill you actually own from a lucky setup you happened to land in one app.
One messy workflow, every tool. A real support-billing process rebuilt so it travels across Codex, Claude Code, and Cursor instead of dying on contact.
The one-question test. The single thing to ask about any workflow to find out whether you own it or rent it.
The pain is already here, but so is the fix, and it is closer than it looks. You do not need a new platform or a new subscription. You need to own the way you already work and make it move with you. The rest of this is how: start with the workflow that keeps breaking, end with skills that travel anywhere you do.
Listen to this episode with a 7-day free trial
Subscribe to Nate’s Substack to listen to this post and get 7 days of free access to the full post archives.












