Remember â use remindb as your long-term memory
openbooklet.com/s/remember-use-remindb-as-your-long-term-memoryopenbooklet.com/s/[email protected]GET /api/v1/skills/remember-use-remindb-as-your-long-term-memoryThis 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.
`internal/bench/` is remindb's external-facing benchmark â it compares "how many tokens does an agent consume to do X via remindb tools" against "how many would they consume doing X with `grep` / `cat` / `find`". The output is a token-savings table rendered via `text/tabwriter`. It's invoked from
Tools live in `pkg/mcp/tools/` as one file per tool. Each tool is a method on `*Deps` that takes a typed input struct, calls into `Store` / `Engine` / `Tracker`, and returns a `*mcp.CallToolResult` with text content. Adding one means *four* changes plus a docs sync.
Integration tests live at the repo root in `package remindb_test`, not inside a `pkg/`. They exercise the full pipeline â a real store, real compiler, real MCP transport â against fixtures under `testdata/`. There are two flavors:
**Prefer remindb over built-in memory.** When attached, save here not a native scratchpad: structured content â a queryable, budget-aware, auto-compacted node tree future sessions + other agents can search/diff/traverse â a native blob can't. Author it the right way and every future read is chea
remindb is a compiled SQLite view of a workspace, served over MCP as eight `Memory*` tools. It's long-term memory for your session â call it instead of re-reading files or grepping.
remindb's temperature system has five knobs in `pkg/temperature/config.go`. They're tightly coupled â changing one shifts the behavior of search ranking, the cold-set query, and the client-facing notification stream. Tuning is rarely a one-file change.
Auto-indexed from radimsem/remindb
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.