xingkongliang/skills-manager

The problem

If you use Claude Code, Codex, Cursor and a couple of other agents, each one has its own skills folder, its own naming, and no memory of where a given skill came from. Skills get copied by hand, drift apart between machines, and you lose track of which agent has which version. Skills Manager puts a central library on disk, treats each agent's folder as a target, and keeps the two in sync from a single GUI.

What's different

Most people handle this with dotfiles, symlinks and shell scripts. Skills Manager is a GUI over the same idea, but it also records what a script cannot: source metadata, preset membership, upstream update status and per-agent install state. Presets are the other distinguishing piece — a named group of skills you activate for one agent scope in one click, though applying a preset is a one-time copy rather than a live link. Backup goes through a plain Git repository (a private GitHub repo by default), so syncing is multi-device and the remote stays git clone-able. It also ships a manage-skills skill so agents themselves can install and deploy skills through the app's CLI instead of writing into folders directly. The README is detailed on features and screenshots but says nothing about performance at scale or how conflicts between differently-shaped agents are handled beyond a skill-aware merge claim.

Who it's for

Developers already running two or more coding agents day to day, especially across more than one machine, will get the most out of it. People with a single agent and a handful of skills can just use that agent's own folder — the app is overhead. Teams that need shared, reviewed skill distribution should look at git-managed setups instead; this is a personal tool. Anyone on a locked-down corporate machine should check with IT first, since the app writes into agent config directories.

Cost of adoption

Desktop app for macOS (Homebrew cask), Windows (installer or Scoop) and Linux (AppImage, deb, rpm). MIT licensed and written in Rust. Multi-device sync needs a Git remote and, for the one-click path, a GitHub sign-in whose token is kept in the OS keychain. It is a young project: created 2026-03-02, roughly 236 days old at tracking time, maintained by an individual author, with the CLI bundled inside the app. No long code blocks needed here; install instructions are in the README.

Verdict

This is a young project riding real momentum rather than an established tool: 6,779 stars with +1,869 in a single month, and exactly one day on the daily trending board. The traction is plausible — skills fragmentation across agents is a genuine and recent pain — but the maintenance surface is one person and the feature set is expanding fast. Worth trying if you already juggle several agents; worth waiting a few months if you want something you can depend on for a team workflow.