# Mem Search

> Use this when the user asks to search memory, "did we already solve this?", "how did we do X last…

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.

- Page: https://ss33.ai/skills/thedotmack/mem-search-67505132173
- Publisher: thedotmack
- Category: [AI & Agents](https://ss33.ai/skills/category/ai-and-agents-y6jz7i) › [Memory & context](https://ss33.ai/skills/category/ai-and-agents-y6jz7i/memory-and-context-5m28a5)
- License: Apache-2.0
- Source: https://github.com/thedotmack/claude-mem/blob/3fae1eb45ba1a7fbd4818527f48b439991a273da/claude-mem-cursor/skills/mem-search/SKILL.md

## Skill

SKILL.md: https://ss33.ai/api/v1/ss33/download/thedotmack/mem-search-67505132173

# 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>`).