thedotmack/claude-mem / cowork/skills/mem-search
mem-search
VerifiedThis skill should be used when the user asks to "search memory", "what do you remember about X", "check claude-mem", "mem search", "find past observations", "what did we do last session", or wants prior-session context about a project, decision, file, or task. Searches the user's Claude-Mem (cmem.ai) memory.
Claude-Mem Search
Search the user's persistent Claude-Mem memory on cmem.ai. Memory contains timestamped observations synthesized from past sessions across all their agents (Claude Code, the Claude app, Codex, and others).
How to search
Run the bundled CLI (no dependencies, uses the plugin's configured API key):
node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" search "your query" --limit 20
Progressive search method
Follow claude-mem's Index → Timeline → Transcript discipline — cheap passes first, expensive detail only for confirmed hits:
- Index pass — run 1–3 broad keyword searches (project names, file names, error strings, feature names). Skim titles/summaries only.
- Narrow pass — re-search with the most specific terms found in step 1
(IDs, exact phrases) and a smaller
--limit. - Answer — synthesize from the observations returned. Quote timestamps when the user asks "when".
Do not dump raw search output at the user; extract the relevant observations and answer in plain language.
Diagnostics
If searches return nothing or error:
node "${CLAUDE_PLUGIN_ROOT}/scripts/cmem-hook.mjs" status
Report the status output plainly: a MISSING api key means the plugin needs the
user's cmem.ai key added to its configuration; a 404 on /api/hooks/context
just means the newer Pro endpoint isn't deployed — search still works via
/api/mcp.
Notes
- Some filters (date ranges, type) may be silently ignored by the cloud API until MCP parity ships — prefer keyword narrowing over filter flags.
- Never write secrets into search queries; queries are sent to cmem.ai.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |