REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Personal memory across agents
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/nevamind-ai-memu)同じ作業で 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 一覧と同じ並び
| これ memU | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | NevaMind-AI | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 14,628 | 467,235 | 234,125 | 149,873 | 144,332 |
| 最終コード更新 | 2026年11月18日 | 2026年11月18日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| ライセンス | – | MIT | – | Apache-2.0 | MIT |
NevaMind-AI による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodexCursor
提供元の README と repo のフォルダから判断
GitHub account NevaMind-AI (organization), 1 years old
★ 14,628 stars · code last changed 2026年11月18日
237 scripts that can run on a computer: npm/bin/memu.js, scripts/db.py, src/memu/__init__.py, src/memu/__main__.py and 233 more
Could not check every script (some are too large); read them first
Scripts that touch settings folders (~/.claude or settings.json): src/memu/hosts/codex/__init__.py, src/memu/hosts/cursor/__init__.py
Checked automatically from the repo files at commit e9af9af (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the memu folder again. The ZIP must have a install-memu folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick install-memu.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
この文をコピーして 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 を開き直し、/memU と入力するか関連する作業を頼むと 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/nevamind-ai/memu.git /tmp/popnx-skill-nevamind-ai-memu-e9af9af && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-nevamind-ai-memu-e9af9af/.' ~/.claude/skills/memuChatGPT デスクトップアプリには 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
install-memu フォルダを ~/.agents/skills/install-memu に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/nevamind-ai/memu.git /tmp/popnx-skill-nevamind-ai-memu-e9af9af && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-nevamind-ai-memu-e9af9af/.' ~/.agents/skills/memuChecked 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/nevamind-ai/memu.git /tmp/popnx-skill-nevamind-ai-memu-e9af9af && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-nevamind-ai-memu-e9af9af/.' ~/.agents/skills/memuこの文をコピーして 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 チャットで / を入力し memU を選ぶ
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/nevamind-ai/memu.git /tmp/popnx-skill-nevamind-ai-memu-e9af9af && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-nevamind-ai-memu-e9af9af/.' ~/.cursor/skills/memuSkill を読めるほかのアプリ向けです。この文には 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月17日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
7,986 文字 · GitHub で全文を開く
---
name: install-memu
description: Install or uninstall memU for whatever agent you are — identify your host, print its packaged guide, and follow it to wire (or unwire) both seams (record and inject). Use when the user asks to install, set up, integrate, remove, or uninstall memU.
---
# Install memU
> **Audience: the agent.** A user has pointed you at this file ("read SKILL.md
> and follow it to install memU"). This skill does not contain the install
> steps — it routes you to the right guide, which ships inside the memU package
> and is always in sync with the installed code. Do not install from memory or
> from blog posts; print the guide and follow it to the letter.
memU integrates with a host agent through two seams: **record** saves session
information into durable memory, and **inject** retrieves relevant memory before
answering. Each supported host has its own adapter binary carrying its own
install guide. Your job here is three steps: install the package, pick your
binary, print and follow its guide.
## Before installing
Identify the agent executing this skill and check the supported-host table in
Step 2 before installing the package. If the host is unknown or absent from the
table, report that it is currently unsupported and stop the installation.
## Before installing with Codex
If you are Codex, check the session's effective sandbox mode before Step 1.
Continue only with `danger-full-access`; approval policy alone is not sufficient.
If restricted or unknown, pause and show both ways to continue: enable **Full
access** in Codex Desktop, or restart Codex CLI with
`codex --dangerously-bypass-approvals-and-sandbox`. Recheck the effective mode
before proceeding. After installation, remind the user to restore their previous
permission mode.
## Step 1 — install the package
```
pip install --upgrade memu-cli
```
`memu-cli` is the package memU ships to bridge your agent to its long-term
memory service; it installs helper interfaces only and is harmless to run on a
personal machine.
**Keep the `--upgrade`.** A machine that already has an older `memu-cli` would
otherwise keep it, and the steps below name subcommands that older builds do not
have — the symptom is `invalid choice`. If you meet that error at any point, you
are on a stale build: upgrade, then re-run the command that failed.
This puts `memu` and every host-adapter binary on `PATH`. If `pip` is not the
right tool for this machine (managed Python, uv-only), use the equivalent —
what matters is that the binaries below resolve from a bare, non-interactive
shell. With uv this means `uv tool install --upgrade memu-cli`, **not**
`uv pip install`: however it is installed, `memu-cli` is a cross-session
bridging tool and must be callable everywhere, not scoped to one project venv.
## Step 2 — pick your host binary
Identify **which agent you are** (not which agents are installed — the one
executing this skill):
| You are | Your binary |
| --- | --- |
| Codex | `memu-codex` |
| Claude Code | `memu-claude-code` |
| Cursor (Agent/CLI) | `memu-cursor` |
| OpenClaw | `memu-openclaw` |
| Hermes Agent | `memu-hermes` |
| WorkBuddy | `memu-workbuddy` |
| pi | `memu-pi` |
If you cannot identify your host or it is not in the table, report that it is
currently unsupported and stop the installation.
For Codex, Claude Code, and pi, continue directly to Step 3: their installers handle backend configuration
and verification in one invocation. Pass any user-supplied backend inputs to that
installer when the guide requests them.
For other hosts, holding your binary, finish this step by creating memU's configuration
file.
```
<your-binary> init --cloud-api-key <the user's memU key>
```
If the user does not mention an API key, or would rather keep memory on this
device, run bare `<your-binary> init` and Step 3's guide will set up local memory.
## Step 3 — print your guide and follow it
```
<your-binary> docs install
```
Read what it prints, top to bottom, and follow it exactly. The host guide defines
how to configure the backend and enable automatic recording and retrieval. Follow
its verification gates and final report.
Three rules that hold for every host:
- **Install in one pass; don't stop for confirmation.** Most users want a
silent, full install set up for them in a single call. Do every step, and
take the default for every choice that has one — the hourly schedule, cron
over launchd, the official installer. Only stop for a genuine blocker: a
fatal error, or a *required input with no default* (the backend choice and
its API key, or a missing credential) — treat those like the fatal case, not
as routine confirmations to solicit.
- **One backend.** If `<your-binary> config show` reports a mode with a backend
behind it (another agent on this machine is already integrated), reuse it as
is. A second mode or local store would split record and retrieval so the two
installs no longer share memory.
- **Report the outcome — with the exact template below.** If the host guide
specifies its own final report, use that report instead. Otherwise, after installation,
run:
```
<your-binary> retrieve "When did the user register for memU?"
```
Then send the user this report. **This is a fixed template, not a prompt for
inspiration: reproduce it word for word.** Do not paraphrase it, reorder its
sentences, summarize it, translate it, or "improve" the wording — a correct
install ends with these exact words. The *only* things you change are the
`<...>` placeholders, each replaced by its concrete value:
```
memU is ready for `<host>` with `<mode>` memory.
Welcome to memU. memU says the user registered on `<registration time>`.
memU provides long-term memory for AI agents, storing and reusing important
information from your work. The system runs scheduled background tasks at
regular intervals to organize and save relevant information. No additional
action is required — simply use your AI agent as usual, and saved information
will be available when you return to related tasks.
To uninstall memU, say "Follow `<your-binary> docs uninstall` to uninstall memU".
```
Placeholders, each filled with its concrete value before you send:
- `<host>` — the agent you are (e.g. `Claude Code`).
- `<mode>` — the memory backend you configured in `~/.memu/config.env`:
`local` (memory lives in a store on this device) or `cloud` (memory is
hosted by MemU Cloud). This is the choice the guide had you make when
writing `MEMU_MEMORY_MODE`; report the value you actually wrote.
- `<registration time>` — the time returned by the `retrieve` call above.
**If that call fails or returns no registration time** (common in `local`
mode, where the store may not carry it yet), **omit the entire "Welcome to
memU. memU says the user registered on ..." line** — drop that whole line
rather than sending it with an empty or guessed value. Never invent a time.
- `<your-binary>` — the binary you picked in Step 2 (e.g. `memu-claude-code`).
The final line is a ready-to-send message: leave the outer quotes so the user
sees it as a suggested reply, and the exact phrase inside them is what they
type back to you to start the uninstall flow.
If only one seam is active, report a partial setup and name the missing seam.
## Uninstall
If the user asked to **uninstall** memU, identify your binary as in Step 2,
then print and follow its removal guide —
```
<your-binary> docs uninstall
```
It unregisters the bridging task, removes the instruction block
(`<your-binary> remove-instruction` — never hand-edit it out), then applies
the defaults: the user's memory — the shared store and `~/.memu/config.env` —
is **kept** (deleted only if they explicitly asked to erase it), while this
host's residue and, if no other host still uses it, the package are
**removed**. Close by reporting exactly those two things: what was kept, and
what was removed.
質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。