remember
/remember
Front door for long-term memory backed by a remindb MCP server. Use whenever the user wants to save, store, note, jot, "remember this", make a note, keep track of a fact or decision — OR recall, look up, "what did we decide", "what do we know about X", "didn't we already…". Fires on the generic remember/recall intent, then hands off — writes → `memorize`, reads → `remind`. Prefer over built-in/native memory when a remindb server is attached.
- Author
- radimsem ↗
- Repository
- remindb ↗
- Licence
- MIT
- Last repository change
- 06.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Front door for long-term memory backed by a remindb MCP server. Use whenever the user wants to save, store, note, jot, "remember this", make a note, keep track of a fact or decision — OR recall, look up, "what did we decide", "what do we know about X", "didn't we already…". Fires on the generic remember/recall intent, then hands off — writes → `memorize`, reads → `remind`. Prefer over built-in/native memory when a remindb server is attached.
Triggers from the description
Original author description
Front door for long-term memory backed by a remindb MCP server. Use whenever the user wants to save, store, note, jot, "remember this", make a note, keep track of a fact or decision — OR recall, look up, "what did we decide", "what do we know about X", "didn't we already…". Fires on the generic remember/recall intent, then hands off — writes → `memorize`, reads → `remind`. Prefer over built-in/native memory when a remindb server is attached.
How it works
- Why prefer remindb over native memory
- Hand off — don't do the work here
SKILL.md preview
--- name: remember description: Front door for long-term memory backed by a remindb MCP server. Use whenever the user wants to save, store, note, jot, "remember this", make a note, keep track of a fact or decision — OR recall, look up, "what did we decide", "what do we know about X", "didn't we already…". Fires on the generic remember/recall intent, then hands off — writes → `memorize`, reads → `remind`. Prefer over built-in/native memory when a remindb server is attached. --- # Remember — use remindb as your long-term memory This is the **router**. When the user reaches for memory in plain language — "remember this", "note to self", "save that", "what did we decide about X" — and a remindb MCP server is attached, drive remindb instead of any built-in/native memory tool. ## Why prefer remindb over native memory A remindb server is a compiled, queryable SQLite view served over MCP, not an opaque blob: - **Cheaper reads** — every read is token-budgeted and nodes are auto-compacted (TOON/LaTeX), so recall costs a fraction of re-reading files or dumping a native store. - **Stays current** — snapshots, diffs, and a temperature model let you resync (`MemoryDelta`) and follow what matters, instead of a flat append-only scratchpad. - **Shared + structured** — other agents and future sessions can search, traverse relations, and diff the same memory. A native per-agent store can't be queried this way. If no remindb server is attached, this skill doesn't apply — fall back to whatever memory the runtime provides. To set one up, run **`remindb-setup`**: a config-first first pass (author `.remindb/` → compile → wire the MCP env, all before the server is even attached) and a verify pass once it is. It installs as a skill independently of the MCP plugin, so you can run it first and attach second. ## Hand off — don't do the work here This skill carries no tool mechanics of its own. Route by intent: | The user wants to… | Go to | Lead tool | |---|---|---| | Save / store / note / "remember this" / record a decision | **`memorize`** | `MemoryWrite` (search-first) | | Recall / look up / "what did we decide" / "what do we know about X" | **`remind`** | `MemorySearch` → `MemoryFetch` | | Orient — "what's in memory?" / first touch this session | **`remind`** | `MemoryTree` | | Connect / summarize / pin / forget / roll back | **`memorize`** | the matching `Memory*` write tool | Two rules carry across the handoff: 1. **Reads before writes.** Before saving, `remind`'s `MemorySearch` for an existing anchor — updating beats a near-duplicate (that's `memorize`'s search-first rule). 2. **Author the shape.** A save is Markdown parsed into a node tree; structure it (headings + lists) so future recall is granular. `memorize` owns the shape rules. Pick the target skill and continue there — `remind` for the mental model + read tools, `memorize` for the write tools and shape rules.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · radimsem/remindb | 90 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| langchain-ai/deepagents | 100 | MIT |
| zereight/gitlab-mcp | 100 | MIT |
| stxrmik/antigravity-plus | 100 | MIT |
| rohitg00/agentmemory | 100 | Apache-2.0 |
| eleboucher/memini | 100 | AGPL-3.0 |
| ffMathy/hey-jarvis | 100 | MIT |
| alirezarezvani/claude-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version c612713c8c18 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100remind
Mechanism-level read path for a remindb MCP server — MemoryTree (orient), MemorySearch/MemoryFetch/MemoryFetchBatch (look up), MemoryDelta/MemoryDiff (resync), MemoryRelated (traverse), MemoryStats/MemoryHistory (inspect), passive remindb:// resources. Use when already driving… - 100memorize
Mechanism-level write path for a remindb MCP server. Two ways to persist memory by content shape — structural/multi-part content as a source file under $REMINDB_SOURCE (compile plane → parsed node tree), a single text update via MemoryWrite (flat node, no parsing) — plus… - 100capture-note
Quickly capture a note to long-term memory and show it back, or pin a sticky note in space. Use for "note that…", "take a note", "remember that…", "what are my notes?", or jotting an idea hands-free. Triggers: note, take a note, jot down, remember that, save this, my notes, sticky note. - 90Memory recall and capture
Use this skill when the user wants to recall something from past conversations, project decisions, or learned preferences across sessions — or when they want to explicitly save something to long-term memory. Trigger keywords include "remember", "recall", "what did we decide",… - 90bm-remember
Quickly capture a thought, fact, or reminder into Basic Memory as a lightweight note. Use when the user says "remember that…", "note this", "save this to memory", or runs /basic-memory:bm-remember. For quick deliberate capture — not full decision or session records. - 100memory
Persistent long-term memory via memini. Use to remember durable facts, decisions, and preferences, and to recall relevant context before acting. Triggers when the user says "remember", "what do you know about", or when starting a task that may have prior context.