REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A lightweight desktop app to manage, sync, and organize AI agent skills across 50+ coding tools — Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/xingkongliang-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 | xingkongliang | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 7,624 | 468,733 | 234,332 | 150,287 | 144,566 |
| Last code change | Nov 14, 2026 | Nov 19, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by xingkongliang 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 CLIGitHub CopilotWindsurfOpenCodeKiro
From the maker’s README and the folders in the repo
GitHub account xingkongliang (person), 12 years old
★ 7,624 stars · code last changed Nov 14, 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 f374817 (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 (604). 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 /manage-skills 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.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
npx skills add xingkongliang/skills-managerCopied from the maker’s README; it downloads and runs the maker’s code
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/xingkongliang/skills-manager.git /tmp/popnx-skill-xingkongliang-skills-manager-f374817 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-xingkongliang-skills-manager-f374817/skills/manage-skills' ~/.claude/skills/manage-skillsThe 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 manage-skills folder at ~/.agents/skills/manage-skills
~ 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/xingkongliang/skills-manager.git /tmp/popnx-skill-xingkongliang-skills-manager-f374817 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-xingkongliang-skills-manager-f374817/skills/manage-skills' ~/.agents/skills/manage-skillsChecked 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/xingkongliang/skills-manager.git /tmp/popnx-skill-xingkongliang-skills-manager-f374817 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-xingkongliang-skills-manager-f374817/skills/manage-skills' ~/.agents/skills/manage-skillsCopy 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 manage-skills
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/xingkongliang/skills-manager.git /tmp/popnx-skill-xingkongliang-skills-manager-f374817 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-xingkongliang-skills-manager-f374817/skills/manage-skills' ~/.cursor/skills/manage-skillsFor 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: manage-skills
description: Manage the user's shared agent-skill library via skills-manager-cli — install, update, remove, deploy or undeploy skills per agent or into a project's own agent directories, manage presets, organize tags, search, and adopt existing skills. Use this whenever the user wants Claude Code, Codex, Cursor, or another agent to gain or lose a skill (globally or in one repo), wants to organize the central library, or asks what is installed or deployed. Prefer this over direct agent-folder installs because Skills Manager preserves source metadata, preset membership, updates, and cross-agent deployment state.
---
## Before doing anything
1. **Resolve the CLI first, then use the path it prints.** Run this once (POSIX
shell):
```bash
D="$HOME/.skills-manager/bin"
B="$D/skills-manager-cli"; [ -e "$B" ] || B="$B.exe" # .exe on Windows
if [ -s "$D/.version" ] && [ -x "$B" ]; then
echo "$B"
elif [ -s "$D/.version" ] || [ -e "$B" ]; then
echo BRIDGE_BROKEN
else
P="$(command -v skills-manager-cli 2>/dev/null || true)"
[ -x "$P" ] && echo "$P"
fi
```
**Substitute the printed path into every command below**, wherever the
examples write `$SM`. Do not carry `$SM` as a shell variable: each command
you run is a new shell, so an assignment made here is gone by the next one.
The three outcomes:
- **A path under `~/.skills-manager/bin`** — the desktop app published this
copy, and the `.version` stamp appears only after it has been verified, so
it always matches the app the user is running. Use it.
- **`BRIDGE_BROKEN`** — something the app left behind is here but does not
add up: an unstamped binary, or a stamp with no binary beside it. Either is
what a copy that failed half-way leaves. **Stop.** Do not go looking
for another CLI: that binary may predate a safety fix, and the machine has
a desktop app whose version nothing here can match. Ask the user to open
the Skills Manager app once, which republishes it.
- **A path from PATH** — nothing was ever published here, so there is no
stale copy to worry about: this is a CLI-only machine (a server install, a
standalone download, a hand-built binary). Use it, but note it can be
older than a desktop app if one is also installed.
If nothing is printed at all, this skill doesn't apply — fall back to
find-skills, or tell the user to install Skills Manager.
2. **Always pass `--json` when you parse output yourself.** Pretty-printed output is for the user; JSON is for you. Errors include `ok=false`, a stable `code`, and `message` on stderr with a non-zero exit code.
```bash
"$SM" --json skills list
```
### When a deployment is refused
A deploy that would overwrite something that is not ours is refused outright —
nothing at those paths is deleted, and nothing else in the batch is applied.
That failure is machine-readable, so report the actual paths rather than the
sentence:
```json
{"ok": false, "code": "TARGET_CONFLICT", "kind": "target_conflict",
"message": "Refusing to deploy: 1 of 2 target(s) …",
"details": {"conflicts": [{"path": "/Users/me/.claude/skills/db",
"reason": "is not a managed deployment"}]}}
```
Tell the user which path is in the way, that its contents are untouched, and
offer the two ways out: adopt it into the library (`skills adopt`), or move it
aside and retry. Never delete it for them.
The project commands refuse the same way, with these `reason`s:
| reason | from | what to tell the user |
|---|---|---|
| `exists and is not this library skill` | `projects deploy` | that directory holds something else; it was left alone and nothing in the batch was written |
| `skills "…" (…) and "…" (…) would both be written here` | `projects deploy` | two library skills have the same directory name and only one can live there; ask the user which one, then deploy just that one |
| `has content not in the library (…)` | `projects undeploy` | the project copy may have edits, extra files (`.gitignore`, `.git`, links) or be a link the user made to somewhere else; `projects import` it first, or remove it with `--force` only if they say it can go |
| `library copy differs from the project copy` | `projects import` | importing would overwrite the library version; `--force` only if they want the project version to win |
| `another copy of this skill also differs from the library` | `projects import` | several agents' copies were edited differently; they must pick one by hand |
Never add `--force` on your own.
## Mental model
There's **one central library** at `~/.skills-manager/skills/` that all agents share. Each skill has source metadata, preset membership, tags, and zero or more real deployments in agent directories. A **preset** is a reusable group; several presets may be deployed at the same time.
Keep these three states separate:
- **Library**: install/remove controls whether Skills Manager owns the skill.
- **Preset membership**: `presets add-skill/remove-skill` organizes the library only.
- **Deployment**: `skills deploy/undeploy` and `presets deploy/undeploy` control what an agent can actually see.
**Project deployments are a separate thing.** `projects deploy` puts a library skill into one project's agent directory (e.g. `<repo>/.claude/skills`). It is not recorded as a deployment: `skills status` and `deployed_to` never show it; read it with `projects show`. Deploying a preset into a project copies its current members once and makes no lasting link.
Internally, presets are still stored as scenarios for backward-compatible Git Backup. The CLI and UI call them presets.
## Install
```bash
# From skills.sh marketplace
"$SM" skills install vercel-labs/agent-skills@react-best-practices
# Any git URL (use /tree/branch/subpath form when the skill lives in a sub-directory)
"$SM" skills install https://github.com/anthropics/skills.git
"$SM" skills install https://github.com/foo/bar/tree/main/skills/baz
# Local folder
"$SM" skills install ./my-skill
# Force a source type when the ref is ambiguous
"$SM" skills install foo/bar --skillssh
"$SM" skills install ./looks-like/owner-repo --local
```
**Default is library-only** — the skill enters the DB but doesn't appear in any agent yet. Prefer an explicit follow-up deployment so scope is unambiguous:
```bash
"$SM" skills deploy <skill> --agent claude_code --agent codex
```
`--sync` and `--sync-preset` remain legacy shortcuts for the exclusive active-preset workflow.
**Ref resolution** is deterministic, no path-existence guessing:
1. Starts with `./`, `../`, `/`, or `~/` → local path
2. Contains `://`, ends in `.git`, or starts with `git@` → git URL
3. Matches `owner/repo`, `owner/repo/skill`, or `owner/repo@skill` → skillssh
4. Otherwise → error; pass `--local` / `--git` / `--skillssh` to disambiguate
**Always verify after install** with `skills list` or `skills show <name>` so you can confirm the skill landed and report the preset / sync state back to the user.
## Search
```bash
"$SM" --json skills search "react performance" --limit 5
```
Each result has `install_ref` (paste straight into `skills install`), `installs` (popularity proxy), and `skills_sh_url`. Show the top 1–3 with install counts before installing — anything with 10K+ installs is battle-tested; anything under 100 needs a careful look at the source repo.
## Update / Check
```bash
# Re-fetch one skill (git/skillssh re-clones, local/import re-imports source dir)
"$SM" skills update <skill-name-or-id>
# Re-fetch all eligible skills
"$SM" skills update --all
# Just probe remote revisions, don't touch files
"$SM" skills check --all
```
`check` is the dry-run partner of `update`. A skill installed from a local folder is compared with that folder, not with any Git remote: `update_available` means the folder changed since it was imported, and `source_missing` means the folder is gone. This check always runs; the cacAsk, 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.