HN Explorer

Skills Manager – manage AI agent skills across Claude, Cursor, Copilot

3 points by evergreenxx ↗ HN
I built a desktop app to manage AI agent skills/rules files across multiple agents (Claude Code, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Goose, Codex).

The problem: each agent stores skills in a different location and in a different format. This gives you one unified view, copy between agents, and install from GitHub repos.

Free and open source: https://sm.idoevergreen.me

21 comments

[ 2.0 ms ] story [ 58.0 ms ] thread
teekert
As someone using agents (like Claude Code), but really not being at home with NPM (never did anything with javascript) etc, I do like this. But, I'm on Linux ;)

I've made some containers for my agents atm (asking them to `ls` and seeing my private ssh key coming by is too scary). My next step is to figure out how to add skills...

prateeksi
The fragmentation problem across agents is real, we ran into the exact same issue managing rules across different dev environments. The unified view approach makes sense, but curious about sync conflicts: if you update a skill file via Cursor and then via Claude Code, does Skills Manager detect the diff or does last-write win? Also wondering if you plan to support team-level skill sharing, not just individual installs from GitHub repos.
druide67
Interesting tool. One thing I've noticed managing rules across Claude Code and Copilot: the same instruction produces very different results depending on the agent. Claude follows multi-step rules well, Copilot tends to ignore anything beyond the first line.

Does Skills Manager handle this at all, or is it purely format/distribution? Seems like the hard problem isn't syncing files — it's that the same "skill" needs different phrasing per agent to actually work.

Dshadowzh
Most of the coding agents support reading skills in ~/.agents/skills. It seems that only Claude code hasn't adopted this spec. I am not sure about the future of this. Anyway good work, we need a unified skill marketplace for different agents.
evergreenxx
Thanks! You're touching on exactly the problem Skills Manager tries to solve — right now it reads from each agent's native path (Claude's ~/.claude/commands, Cursor rules, Windsurf, etc.), so you manage one set of skills that syncs across all of them.

The ~/.agents/skills spec is interesting—if it gains real adoption, we'd support it as a source path as well. Skills Manager is intentionally agent-neutral, so adding a new path resolver is trivial.

QubridAI
That’s a great idea! It seems like we’re already running into 'tooling sprawl' with AI agents, and this is a good move to help manage it.