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.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/jiweiyeah-skills-manager)같은 작업에서 AI를 서비스에 연결하는 MCP
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
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 Skills-Manager | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | jiweiyeah | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 1,064 | 467,235 | 234,125 | 149,873 | 144,332 |
| 마지막 코드 변경 | 2026년 9월 10일 | 2026년 11월 18일 | 2026년 4월 20일 | 2026년 11월 18일 | 2026년 11월 18일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
jiweiyeah의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeCodexCursorGemini CLIWindsurfOpenCode
제작자 README와 repo 폴더 기준
GitHub account jiweiyeah (person), 2 years old
★ 1,064 stars · code last changed 2026년 9월 10일
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
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (623). Use "Let the AI install it" instead
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
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
Claude Code를 다시 열고 /skills-manager-cli를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 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-cliChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
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
skills-manager-cli 폴더를 ~/.agents/skills/skills-manager-cli에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 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 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
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는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 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-cli이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
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
Cursor Agent 채팅에서 /를 입력하고 skills-manager-cli 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 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-cliSkill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · 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 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
✓ 명령 확인 2026년 11월 18일
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · 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 --jso질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.