|
| 1 | +--- |
| 2 | +name: nowledge-mem-guide |
| 3 | +description: > |
| 4 | + Cross-AI personal knowledge graph memory (Nowledge Mem). Stores memories from this tool, |
| 5 | + Claude Code, Cursor, browser capture, imported documents, and more. Use when: (1) the user |
| 6 | + asks about prior work, decisions, preferences, people, dates, plans, or todos, (2) the user |
| 7 | + references something discussed before or says "remind me" / "what did we decide" / "what was |
| 8 | + I working on", (3) the conversation produces a decision, preference, plan, or learning worth |
| 9 | + keeping, (4) the user wants to browse recent activity or explore how ideas connect, (5) the |
| 10 | + user asks about a past conversation or wants to find a specific thread. |
| 11 | +--- |
| 12 | + |
| 13 | +# Nowledge Mem |
| 14 | + |
| 15 | +## Search (memory_search) |
| 16 | + |
| 17 | +Use natural language queries. This is semantic search, not file search. |
| 18 | + |
| 19 | +- "database choice for task events" (not "MEMORY.md" or file paths) |
| 20 | +- "meeting with Sarah about API redesign" |
| 21 | +- "deployment procedure for production" |
| 22 | + |
| 23 | +Results include `matchedVia` (scoring breakdown), `importance`, `labels`, `sourceThreadId`. |
| 24 | + |
| 25 | +When results include `relatedThreads`, use `nowledge_mem_thread_fetch` with the `threadId` for full conversation context. Start with a small page; fetch more via `offset` + `limit` only when needed. |
| 26 | + |
| 27 | +Bi-temporal filters narrow results by time: |
| 28 | + |
| 29 | +- `event_date_from` / `event_date_to` — when the fact happened |
| 30 | +- `recorded_date_from` / `recorded_date_to` — when it was saved |
| 31 | + |
| 32 | +## Save (nowledge_mem_save) |
| 33 | + |
| 34 | +Save proactively when the conversation produces a decision, preference, plan, procedure, learning, or important context. Do not wait to be asked. |
| 35 | + |
| 36 | +Structure saves: |
| 37 | + |
| 38 | +- `unit_type`: fact | preference | decision | plan | procedure | learning | context | event |
| 39 | +- `labels`: lowercase-hyphenated topic tags |
| 40 | +- `importance`: 0.0-1.0 (most: 0.5; key decisions/preferences: 0.7-0.9) |
| 41 | +- `event_start` / `event_end`: ISO dates when temporal |
| 42 | + |
| 43 | +Skip trivial exchanges, greetings, and meta-conversation about memory itself. |
| 44 | + |
| 45 | +## Connections (nowledge_mem_connections) |
| 46 | + |
| 47 | +Pass a `memoryId` from search results to explore related memories, evolution chains, and source documents. Edge types: EVOLVES, CRYSTALLIZED_FROM, SOURCED_FROM, MENTIONS. |
| 48 | + |
| 49 | +## Timeline (nowledge_mem_timeline) |
| 50 | + |
| 51 | +Browse recent activity grouped by day. Filter by `event_type` or exact `date_from` / `date_to` range. |
| 52 | + |
| 53 | +## Threads (nowledge_mem_thread_search + nowledge_mem_thread_fetch) |
| 54 | + |
| 55 | +Find past conversations by keyword, then progressively fetch messages. Threads span all sources: this tool, other AI tools, browser capture, imports. |
| 56 | + |
| 57 | +## Working Memory (nowledge_mem_context) |
| 58 | + |
| 59 | +Read the user's daily briefing (priorities, active projects, flags). Patch a specific section with `patch_section` + `patch_content`/`patch_append` when the conversation updates a priority or resolves a flag. |
| 60 | + |
| 61 | +## Important |
| 62 | + |
| 63 | +- Search uses natural language queries, not file paths. Never search for "MEMORY.md" or "memory/*.md". |
| 64 | +- When `relatedThreads` appear in results, they often contain the most useful context. |
| 65 | +- Use tools directly; do not tell the user to "check your memory." |
0 commit comments