skills-manager-cli
Drive the Skills Manager CLI (`skm`) to initialize the hub, adopt unmanaged skills, list/enable/disable skills per AI tool, and doctor/fix symlink sync. Use whenever the user or an agent needs to manage skills from a terminal, SSH session, CI job, or headless machine; when a skill is missing in Claude Code, Codex, Cursor, Gemini, OpenCode, or any other supported tool; when asked to run skm / Skills Manager CLI; or when setting up Skills Manager without the GUI. Do not use for `npx skills` / skills.sh search (different CLI), for writing SKILL.md content (skill-creator), or for marketplace browse/install (not in skm).
jiweiyeah · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add jiweiyeah/Skills-Manager --skill skills-manager-cliAbout this skill
name: skills-manager-cli
description: >
Drive the Skills Manager CLI (skm) to initialize the hub, adopt unmanaged
skills, list/enable/disable skills per AI tool, and doctor/fix symlink sync.
Use whenever the user or an agent needs to manage skills from a terminal,
SSH session, CI job, or headless machine; when a skill is missing in Claude
Code, Codex, Cursor, Gemini, OpenCode, or any other supported tool; when
asked to run skm / Skills Manager CLI; or when setting up Skills Manager
without the GUI. Do not use for npx skills / skills.sh search (different
CLI), for writing SKILL.md content (skill-creator), or for marketplace
browse/install (not in skm).
Skills Manager CLI (skm)
New here? This skill drives skm, the command-line tool that ships with
Skills Manager — a desktop app
(macOS / Windows / Linux) that installs one copy of a skill into a central hub
and symlinks it into every AI coding tool you use (Claude Code, Codex, Cursor,
Gemini, and ~30 more), so you write a skill once and it shows up everywhere.
If you found this skill on ClawHub but don't have Skills Manager yet, that is
the missing piece: skm is not a standalone binary you npm install. Get it
by installing the app from the official website
(then Settings → Command Line Tool, or run skm init), or grab a
skm-<target>.tar.gz / .zip from the
GitHub Releases page.
Source and docs: https://github.com/jiweiyeah/skills-manager.
skm is the terminal front-end of Skills Manager. It reads and writes the
same ~/.skills-manager/config.json and the same hub/tool symlinks as the
desktop app, so GUI and CLI are interchangeable.
It does not create, edit, search, translate, tag, or marketplace-install
skills. Those stay in the GUI (or you write files into the hub yourself, then
skm enable).
Preconditions
- Resolve the binary. Prefer
skmonPATH. If missing, say so and point at install: the Skills Manager app (Settings → Command Line Tool), or a release archiveskm-<target>.tar.gz/.zipfrom GitHub Releases. Do not fall back tonpx skills— that is a different, unrelated CLI. - Confirm with
skm --version. A stale binary from an older app release should be updated from Settings or a matching release. - Every command except
initrequires an initialized config. If stderr says so, runskm init --jsononce — it is idempotent and will not clobber an existing config.skm initand Settings → Install CLI also copy this companion skill into the hub and enable it for every currently active tool, so you usually do not need to install it by hand.
Hub path is fixed at ~/.skills-manager/skills (%USERPROFILE%\.skills-manager\skills
on Windows). save() always rewrites skills_dir to that default; there is
no supported way to pick another hub from the CLI.
Agent conventions
These exist because skm is designed to be called by agents, not just humans.
- Prefer
--jsononinit,list,doctor,fix, andadopt(apply). Data is one JSON document on stdout. Errors go to stderr as{"error":"..."}when the command was in JSON mode, otherwiseerror: .... A command can print a result on stdout and still exit 1 (fixwith failed repairs) — parse stdout, then trust the exit code. enable/disablehave no--json. Success is a one-lineenabled '<id>' for '<tool>'(ordisabled). Failure iserror: ...on stderr, exit 1.- Never wait on a TTY prompt.
adoptwithout--yesand without--jsonblocks on[y/N]. Pass--yeswhen applying.--jsonalso skips the prompt (and therefore applies) — still pass--yesso the intent is obvious in the command line. skm adopt --json --dry-runis not a machine-readable preview: if candidates exist it prints nothing. Preview withskm adopt --dry-run(human text), then apply withskm adopt --yes --json.doctor --jsonexits 0 even when there are issues. Gate on.issues_count, not the exit code.fixwithout--yesdoes not repair. JSON then looks like{"applied": false, "issues_found": N, ...}. Apply withskm fix --yes --json.- Write commands (
init,adopt,enable,disable,fix --yes) take an advisory lock onconfig.jsonand fail fast if anotherskmis mid-write. Retry once. The desktop app does not take this lock. - Do not enable a skill for every detected tool unless the user asked. Pick the tool they named, or the host agent (see Which tool).
JSON shapes, exit codes, and the dry-run/apply matrix live in
references/json.md. Read that before parsing output or writing a script.
Command map
| Intent | Command |
|---|---|
| First-run / is it initialized? | skm init --json |
| What skills exist, and where are they linked? | skm list --json |
| Same, one tool only | skm list --tool <id> --json |
| Turn a hub skill on for a tool | skm enable <skill> --for <tool> |
| Turn it off (remove the link, keep the hub copy) | skm disable <skill> --for <tool> |
| Which tools are installed, any broken links? | skm doctor --json |
| Repair what doctor reported | skm fix --yes --json |
| Preview leftover real dirs in tool skill folders | skm adopt --dry-run |
| Move those dirs into the hub and relink | skm adopt --yes --json |
<skill> and <tool> accept an exact id, an exact instance_id, or a
unique prefix (claude → claude-code). Ambiguous prefixes error and
list the matches — do not guess, rerun with a longer token. Exact tool id
wins before prefix (trae is Trae, not Trae CN). Full ids and collision
notes: references/tools.md.
Workflows
First-run on a machine with no GUI
Read the complete source ↗