If you bounce between Claude Code, Cursor, Codex, whatever, you’ve probably hit this: you write a genuinely useful skill, save it in one tool, and then it’s stuck there. New laptop, different agent, and you’re copy-pasting files around or just rewriting the thing. I did this enough times to get annoyed and build something. It’s called skills-registry. The idea is simple: your skills live in one GitHub repo that you own, and every agent on every machine reads from that same repo. Write a skill once, it shows up everywhere. Any agent, on any machine, can pull all your personal skills through the skills-registry CLI. Open Source and Free. Setup is one command: npx skills-registry A little terminal UI takes it from there. It scans your machine for skills you’ve already got scattered across different tool folders, makes the repo, pushes everything up, and wires up whichever agents you want to use. Then it offers to delete the leftover local copies and leaves you with a single skill. You don’t touch git and you don’t hand-edit any JSON.
Quick demo I told my agent: “humanize this Reddit post.” It had no humanizer skill loaded. Just the one tiny gateway skill. So it went and got one: $ skills-registry search humanizer → humanizer — remove signs of AI-generated writing from text $ skills-registry get humanizer → fetched
It read the skill, applied it to my draft, and then offered to delete the local copy since it was already in context. The humanizer skill itself was never loaded until the moment it was actually needed — and it was gone again right after. That’s the whole pitch in one interaction. One skill loaded, everything else fetched on demand. The part I keep coming back to is the context savings. Normally if you want your agent to have access to a bunch of skills, you load them all up front and they sit there eating your context window whether you use them or not. Here you load exactly one small skill. That one skill knows how to search the registry and pull down whatever you actually need, right when you need it. Your agent can reach an unlimited number of private skills while only paying for one being loaded. No more cramming hundreds of skills into the context on the off chance one comes up. In practice it just means I stop thinking about where a skill lives. I write it once, and the next time I’m on a different machine in a different tool, it’s there. It’s open source. I’d genuinely like to hear where it breaks or what’s confusing, and I’m curious what people end up building with it. There’s a desktop mac app available as well for managing your skills repo, and a remote MCP too if you need to load skills on the web. https://github.com/anand-92/skills-registry submitted by /u/waxyslave
Originally posted by u/waxyslave on r/ClaudeCode