Agent skill · writing content · thedotmack
mem-search
Search claude-mem'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.
Why this skill is useful
Provides specific commands and workflows for efficiently searching and retrieving past session data that the AI wouldn't generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-05. 89,894 stars on the source repository.
What this skill does
Memory Search Search past work across all sessions. Simple workflow: search -> filter -> fetch -> (rarely) disclose raw tool I/O. When to Use Use when users ask about PREVIOUS sessions (not current conversation): "Did we already fix this?" "How did we solve X last time?" "What happened last week?" Layered Workflow (ALWAYS Follow) NEVER fetch full details without filtering first. 10x token savings. Step 1: Search - Get Index with IDs Use the search MCP tool: Returns: Table with IDs, timestamps, types, titles (~50-100 tokens/result) Parameters: query (string) - Search term limit (number) - Max results, default 20, max 100 project (string) - Project name filter type (string, optional) - "observations", "sessions", or "prompts" obstype (string, optional) - Comma-separated: bugfix, feature, decision, discovery, change dateStart (string, optional) - YYYY-MM-DD or epoch ms dateEnd (string, optional) - YYYY-MM-DD or epoch ms offset (number, optional) - Skip N results orderBy (string, optional) - "datedesc" (default), "dateasc", "relevance" Step 2: Timeline - Get Context Around Interesting Results Use the timeline MCP tool: Or find anchor automatically from query: Returns: depthbefore + 1 + depthafter items in chronological order with observations, sessions, and prompts interleaved around the anchor. Parameters: anchor (number, optional) - Observation ID to center around query (string, optional) - Find anchor automatically if anchor not provided depthbefore (number, optional) - Items before anchor, default 5, max 20 depthafter (number, optional) - Items after anchor, default 5, max 20 project (string) - Project name filter Step 3: Fetch - Get Full Details ONLY for Filtered IDs Review titles from Step 1 and context from Step 2. Pick relevant IDs. Discard the rest. Use the getobservations MCP tool: ALWAYS use getobservations for 2+ observations - single request vs N requests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills thedotmack/mem-search