REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Personal memory across agents
Wenn du das gebaut hast, füge diesen Code in dein README ein. Das Badge verlinkt auf diese Seite.
[](https://mcp.popnx.com/en/skills/nevamind-ai-memu)MCP-Server, die die KI für dieselbe Arbeit mit Diensten verbinden
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
Gleiche Art Arbeit, sortiert wie die Skill-Liste
| Dieser memU | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Anbieter | NevaMind-AI | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub-Sterne | 14.628 | 467.235 | 234.125 | 149.873 | 144.332 |
| Letzte Codeänderung | 18. Nov. 2026 | 18. Nov. 2026 | 20. Apr. 2026 | 18. Nov. 2026 | 18. Nov. 2026 |
| Lizenz | – | MIT | – | Apache-2.0 | MIT |
1 Skills (Anweisungssammlungen) von NevaMind-AI, die eine KI liest und befolgt · kein MCP-Server
MCP = die Hände
Verbindet die KI mit einem externen Dienst oder Daten, etwa Notion lesen oder eine Rechnung erstellen. Ein Programm oder Server muss laufen.
Skill = das Handbuch
Eine Textdatei, die der KI zeigt, wie eine Aufgabe geht. Sie verbindet sich mit nichts.
Manches überschneidet sich: Einige Skills starten Skripte mit Werkzeugen, einige MCP-Server liefern nur Wissen. Geh von der Aufgabe aus.
Claude CodeCodexCursor
Laut README des Anbieters und den Ordnern im Repo
GitHub account NevaMind-AI (organization), 1 years old
★ 14.628 stars · code last changed 18. Nov. 2026
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
Zuerst: Welche KI nutzt du?
Wähle deine App, dann zeigt diese Seite nur die Installation für diese App
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 12. Nov. 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Kopiere diesen Satz und füge ihn in einen Claude Code-Chat ein
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 neu starten, dann /memU tippen oder eine passende Aufgabe stellen; Claude nutzt den Skill
Checked against official docs 12. Nov. 2026 · Source: code.claude.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer 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/memuSelbst installierte Skills funktionieren in der ChatGPT-Desktop-App, in Codex CLI und in der Codex-Erweiterung für die IDE · ChatGPT im Web und auf dem Handy kann selbst installierte Skills nicht nutzen, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen
Die ChatGPT-Desktop-App enthält Codex, und Codex liest Skills aus dem Ordner ~/.agents/skills
Öffne Codex in der ChatGPT-Desktop-App und füge diesen Satz in den Chat ein
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
Lege den Ordner install-memu unter ~/.agents/skills/install-memu ab
~ ist dein Home-Ordner ($HOME)
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer 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 15. Nov. 2026 · Source: learn.chatgpt.com
Selbst installierte Skills funktionieren hier nicht, nur Skills, die mit einem Plugin aus dem Verzeichnis kommen
Um diesen Skill mit ChatGPT zu nutzen, verwende die ChatGPT-Desktop-App wie oben beschrieben
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Kopiere diesen Satz und füge ihn in einen Codex-Chat ein · Funktioniert in Codex in der ChatGPT-Desktop-App, in Codex CLI und in der IDE-Erweiterung
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 erkennt neu installierte Skills selbst; wenn einer nicht erscheint, starte Codex neu · So nutzt du ihn: In ChatGPT @ tippen und den Skill wählen · in Codex CLI oder der IDE-Erweiterung /skills ausführen oder $ und den Skill-Namen tippen
Checked against official docs 15. Nov. 2026 · Source: learn.chatgpt.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer 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/memuKopiere diesen Satz und füge ihn in einen Cursor-Chat ein
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
Im Agent-Chat von Cursor / tippen und memU wählen
Checked against official docs 12. Nov. 2026 · Source: cursor.com
Ein Skill sind Anweisungen, denen die KI folgt. Lies die Dateien vor der Installation und installiere nur von vertrauenswürdigen Anbietern.
Mac: Command+Leertaste und Terminal tippen · Windows: Der Befehl unten funktioniert nicht in PowerShell; nutze oben „KI installiert es“
Lädt das Repo in einen temporären Ordner und kopiert nur Ordner mit einer 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/memuFür andere Apps, die Skills lesen. Der Satz enthält die Pfade für Claude Code, Codex und Cursor, damit die KI den für deine App wählt · 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 12. Nov. 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Andere Apps mit Agent Skills (etwa Gemini CLI oder GitHub Copilot) nutzen andere Ordner. Sieh in deren Anleitung nach und kopiere den Ordner mit der SKILL.md dorthin.
Skill-Ordner am 11. Nov. 2026 mit den offiziellen Anleitungen von Claude Code, Codex und Cursor geprüft
✓ Befehle geprüft am 17. Nov. 2026
Der folgende Text stammt aus dem Repo des Anbieters, nicht von PopNx MCP
7.986 Zeichen · Ganze Datei auf GitHub öffnen
---
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.
Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.
Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.
Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.