Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jiweiyeah/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.
Passed 13 of 18 test cases with the skill, and 3 of 18 without it.
and 18 more in the full report
13 fixed4 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just created a brand new folder '~/.skills-manager/skills/rust-helper' and added a valid SKILL.md inside it. What is the next skm command I must run to make rust-helper active in OpenCode?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends running skm enable rust-helper --for opencode. | Missed | Passed |
| Recommends running skm list --tool opencode --json to verify registration. | Missed | Passed |
The instructions your model reads when the skill loads.
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).
skm on PATH. If missing, say so and point
at install: the Skills Manager app
(Settings → Command Line Tool), or a release archive
skm-<target>.tar.gz / .zip from
GitHub Releases.
Do not fall back to npx skills — that is a different, unrelated CLI.skm --version. A stale binary from an older app release
should be updated from Settings or a matching release.init requires an initialized config. If stderr
says so, run skm init --json once — it is idempotent and will not
clobber an existing config. skm init and 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.test cases passed, vs 3 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.