Skills Manager CLI
A CLI and manager skill: one skills library distributed to 70+ agents, with management done from the agent conversation
- 243 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Creates symlinks and copies files into Claude Code, Codex, Cursor and other agent folders
- Downloads skills from git, URLs and archives, and a third-party skill carries instructions the agent follows
- Import moves your existing skills into the hub, backed up first
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/shenysun-skills-managerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Creates symlinks and copies files into Claude Code, Codex, Cursor and other agent folders
- Downloads skills from git, URLs and archives, and a third-party skill carries instructions the agent follows
- Import moves your existing skills into the hub, backed up first
This is third-party code. Review the repository files before installing.
What it does
Skills Manager (the skills-manager-cli package) creates a `~/.skills-manager` hub with one `npx skills-manager-cli` command, drops the manager skill into it and symlinks it into the agents it finds on the machine. From there install, import, distribute, update and provenance backfill all happen in conversation with the agent, while the CLI underneath works as a JSON engine. Skills come from five sources: git repositories and URLs, direct links to SKILL.md, zip and tar, local archives, Claude plugin marketplaces and well-known indexes. Any subset of the library goes to any catalog agent by symlink or copy, with stale-copy detection and rollback. Updates are keyed on the git tree hash of the skill's own subfolder, so unrelated commits in the repository never raise false alarms. The `cost` command accounts how much context the descriptions of distributed skills take on each message. `check`, `audit overlap`, `audit descriptions` and `trigger test` check description overlaps and routing without a model, which suits CI. For several machines the hub syncs through git.
Who it is for. People who keep dozens of skills across several agents and want one library instead of copies across the Claude Code, Codex and Cursor folders.
Good fit when
- The same skills sit as copies in ~/.claude/skills and other agents' folders and need merging into one hub
- You need to know which skills have updates, without false alarms
- Skill descriptions eat context and you want to see what each one costs
- CI needs a check that a request triggers the right skill and a search for overlapping descriptions
- The skills hub must sync between two computers
Not a fit when
- You need a desktop app with windows: the project is a terminal and npm tool with a local web dashboard, not a desktop client
- Skills are for one agent and installed once: npx skills add is simpler
- You need to deliver skills into a closed network without npm: the tool ships through npx
Example request
Take stock of my skills: what I have, which agents they are wired into and what has updatesLimitations
The project differs from the desktop client with the same name in another repository, so do not mix them up. The context-cost estimate is approximate and marked with an approximation sign. The agent count, over 70, comes from a directory snapshot and may differ from your version. For non-GitHub sources such as direct links and archives, the tree-hash update mechanism works only in part because it relies on git history.
How to disable. Remove the hub and binaries: npm uninstall -g skills-manager-cli and the ~/.skills-manager folder. Delete symlinks in agent folders by hand; skills imported earlier were backed up before import.
FAQ
How does it differ from npx skills and gh skill?
One hub for every agent, updates by the skill subtree hash, a context cost ledger, description quality checks for CI and multi-machine sync. Installers such as npx skills install a skill once.
How do I bring in skills I already have?
Ask the agent to import existing skills into skills-manager. Content moves into the hub and originals become symlinks after a backup. Preview the plan first with skills-manager init --dry-run.
What does the cost command do?
Counts how much context the descriptions of distributed skills take on each message, per runtime path. cost --share prints a paste-ready card without absolute paths.
Can skills be checked in CI?
Yes: check, audit security --strict, audit overlap, audit descriptions and trigger test run without a model. The repository includes GitHub Actions workflow examples.
Is there a web interface?
There is an optional local web dashboard. The main way to manage stays the agent conversation.
Discussion
No questions or reviews yet.
Related
CLI toolsA desktop app and CLI to install, sync and organize agent skills across Claude Code, Codex, Cursor and other tools
A command-line skill manager: installs skills from a marketplace, GitHub, private Git and npm into 45 agents' folders and scans them first
skills (npx skills)
skills
A skill package manager: installs, finds, updates and removes SKILL.md packages from GitHub and other git hosts across many agents
A CLI skill manager for AI agents: install from repositories, translate between agent formats and deploy into their configs
A skill that searches three skill catalogs, installs with a scan and compares copies across Claude Code, Codex and Cursor.
A CLI installer and package manager for coding agent skills: one command installs skills into many runtimes and helps build your own
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Skills Manager (this card) | no | 243 | |
| Skills Manager | no | 7,468 | a desktop client with a GUI; this one is a CLI with conversation-driven management and CI checks |
| Universal Skills Manager | no | 115 | a skill for installing and tracking skills; this one adds a shared hub, per-agent distribution and audits |
README in short
The description builds on managing skills from conversation. It then gives a comparison table with gh skill, npx skills and the desktop client, a quick start and a command list for migration, CI checks and hub sync.