REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Free, open-source desktop manager for AI Agent Skills. Write a skill once, sync it to 32 AI coding tools (Claude Code, Codex, Cursor, Gemini CLI, and more) via symlinks. Local-first, MIT licensed. macOS, Windows, Linux.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/jiweiyeah-skills-manager)MCP servers that connect the AI to services for the same work
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
Same kind of work, ordered like the Skills list
| This one Skills-Manager | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | jiweiyeah | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 1,064 | 467,235 | 234,125 | 149,873 | 144,332 |
| Last code change | Sep 10, 2026 | Nov 18, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by jiweiyeah that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude CodeCodexCursorGemini CLIWindsurfOpenCode
From the maker’s README and the folders in the repo
GitHub account jiweiyeah (person), 2 years old
★ 1,064 stars · code last changed Sep 10, 2026
No, plain text files the AI reads and follows
No scripts, so it does not go online by itself
No hooks or writes to machine settings found
Checked automatically from the repo files at commit bc3c8bd (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Uploading to claude.ai would fail: the description is over 200 characters (623). Use "Let the AI install it" instead
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /skills-manager-cli or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/jiweiyeah/skills-manager.git /tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd/skills/skills-manager-cli' ~/.claude/skills/skills-manager-cliThe ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the skills-manager-cli folder at ~/.agents/skills/skills-manager-cli
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/jiweiyeah/skills-manager.git /tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd/skills/skills-manager-cli' ~/.agents/skills/skills-manager-cliChecked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/jiweiyeah/skills-manager.git /tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd/skills/skills-manager-cli' ~/.agents/skills/skills-manager-cliCopy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick skills-manager-cli
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/jiweiyeah/skills-manager.git /tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-jiweiyeah-skills-manager-bc3c8bd/skills/skills-manager-cli' ~/.cursor/skills/skills-manager-cliFor other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 18, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
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**](https://skillsmanager.freeourdays.com) — 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](https://skillsmanager.freeourdays.com/?ref=clawhub#download)
(then Settings → Command Line Tool, or run `skm init`), or grab a
`skm-<target>.tar.gz` / `.zip` from the
[GitHub Releases page](https://github.com/jiweiyeah/skills-manager/releases).
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
1. Resolve the binary. Prefer `skm` on `PATH`. If missing, say so and point
at install: the [Skills Manager app](https://skillsmanager.freeourdays.com/?ref=clawhub#download)
(Settings → Command Line Tool), or a release archive
`skm-<target>.tar.gz` / `.zip` from
[GitHub Releases](https://github.com/jiweiyeah/skills-manager/releases).
Do not fall back to `npx skills` — that is a different, unrelated CLI.
2. Confirm with `skm --version`. A stale binary from an older app release
should be updated from Settings or a matching release.
3. Every command except `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.
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 `--json` on `init`, `list`, `doctor`, `fix`, and `adopt` (apply).
Data is one JSON document on stdout. Errors go to stderr as
`{"error":"..."}` when the command was in JSON mode, otherwise
`error: ...`. A command can print a result on stdout and still exit 1
(`fix` with failed repairs) — parse stdout, then trust the exit code.
- `enable` / `disable` have no `--json`. Success is a one-line
`enabled '<id>' for '<tool>'` (or `disabled`). Failure is `error: ...`
on stderr, exit 1.
- Never wait on a TTY prompt. `adopt` without `--yes` and without `--json`
blocks on `[y/N]`. Pass `--yes` when applying. `--json` also skips the
prompt (and therefore applies) — still pass `--yes` so the intent is
obvious in the command line.
- `skm adopt --json --dry-run` is not a machine-readable preview: if
candidates exist it prints nothing. Preview with `skm adopt --dry-run`
(human text), then apply with `skm adopt --yes --json`.
- `doctor --json` exits 0 even when there are issues. Gate on
`.issues_count`, not the exit code.
- `fix` without `--yes` does not repair. JSON then looks like
`{"applied": false, "issues_found": N, ...}`. Apply with `skm fix --yes --json`.
- Write commands (`init`, `adopt`, `enable`, `disable`, `fix --yes`) take
an advisory lock on `config.json` and fail fast if another `skm` is
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](#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
```bash
command -v skm
skm init --json
skm adopt --dry-run
skm adopt --yes --json
skm list --json
skm doctor --json
```
`init` on an already-initialized config returns
`{"already_initialized": true, ...}` and does nothing else. If
`config.json` exists but cannot be parsed, `init` refuses to overwrite it
— move or fix the file, then retry.
### Make an existing hub skill available to a tool
```bash
skm list --json # find id / instance_id
skm enable <skill> --for <tool>
skm list --tool <tool> --json # confirm enabled_for
```
Enabled state is derived from the link on disk, not stored as a separate
flag. `enable` creates the symlink (Windows: symlink → junction → tracked
copy). `disable` removes that link; the hub copy stays.
If the same skill id exists in both global and the active project, a bare
id is ambiguous. Use the `instance_id` from `list`: `global:<id>` or
`project:<project_id>:<id>`.
### Add a brand-new skill (CLI cannot scaffold it)
1. Write `~/.skills-manager/skills/<id>/SKILL.md` with YAML `name` +
`description`. A directory is a skill if it contains `SKILL.md`,
`skill.md`, or `meta.json`.
2. `skm enable <id> --for <tool>`
3. `skm list --tool <tool> --json` to confirm.
Do not copy the folder into `~/.claude/skills` (or any other tool dir)
yourself — that bypasses the hub and `adopt` will later see it as an
unmanaged real directory.
### Adopt skills that already live in a tool directory
`adopt` looks at **active** tools (enabled + detected) for real
directories that are not symlinks/junctions and not hidden. It **moves**
each one into the hub, then puts a link back at the original path.
- Duplicate hub names are skipped and left in place (contents are not
merged — they may differ).
- Preview first (`--dry-run`), then apply (`--yes --json`).
- After apply, `list` should show the new ids as enabled for the source
tool.
### Diagnose "the skill is not showing up in Claude / Codex / …"
```bash
skm doctor --jsoAsk, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.