mem-search

Featured

Use this when the user asks to search memory, "did we already solve this?", "how did we do X last time?", or wants work from previous sessions.

AI & Automation 93,663 stars 8238 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
35
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# mem-search Layered workflow. Do not dump full observations until IDs are filtered, and do not reach for raw tool bodies until the summaries came up short. 1. `search(query)` — index with IDs 2. `timeline(anchor=ID)` — nearby context 3. `get_observations(ids=[...])` — full details for those IDs only 4. `get_tool_uses(ids=[...])` — the ORIGINAL `tool_input` / `tool_response` for specific tool calls. Last resort: these are unsummarized and can run to thousands of tokens each. Stamp `platformSource` as `cursor` or `grok-bot` on writes for this host. When reading, do not drop the other host unless asked. If MCP is missing, run the install skill first (`npx claude-mem install --ide <host>`).

Details

Author
thedotmack
Repository
thedotmack/claude-mem
Created
1 years ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Integrates with

Anthropic · AI SQLite · Database ChromaDB · Database

Bundled in these plugins

claude-mem

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

mem-search

Search keepmind's persistent cross-session memory database. Use when user asks "did we already solve this?", "how did we do X last time?", or needs work from previous sessions.

1 Updated 1 weeks ago
ManuelStaggl
AI & Automation Listed

mem-search

Search persistent project memory across sessions — decisions, bugs, features, discoveries

3 Updated today
djnsty23
AI & Automation Featured

memory-recall

Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Memory available` hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.

2,589 Updated today
zilliztech