-
Notifications
You must be signed in to change notification settings - Fork 1
FAQ
Home | Quick Start | Safety and Data
Not yet. The npm package name is reserved, but the documented installation path is git clone:
git clone https://github.com/GrubbyLee/skill-manager.git
cd skill-manager
node scripts/install.mjsskm is the same as skm status. It prints a health overview: total skills, MCP count, never-used skills, duplicate installs, session log size, health score, and suggested next commands.
No. It writes ~/.skill-manager/catalog.json for skm's own inventory cache. It does not edit skills, configs, MCP servers, or session logs.
It looks for real usage signals in session logs. Codex may inject all skill paths into context, but skm only counts actual skill reads or calls as usage.
The current usage signal for idle MCP comes from Claude-side logs. Codex-only MCP servers are reported as unobservable instead of being treated as idle.
Use JSON output:
skm scan --json > scan.json
skm list --json > skills.json
skm list --mcp --json > mcp.jsonIn the HTML graph:
- turn off same category and shared platform first
- enable important-node mode
- hide never-used skills
- use search to focus a topic
- drag local clusters by hand
- click fit view after filtering
skm doctor
skm scan
skm
skm risks
skm report --format html --output skm-report.html
skm sessions --clean --days 30 --keep 3 --dry-runOnly remove --dry-run after reviewing the plan.
Built for local Claude Code / Codex skill governance. Repository: skill-manager.