Claude-Mem Search Skill

Access claude-mem's persistent memory through a comprehensive HTTP API. Search for past work, understand context, and learn from previous decisions.

When to Use This Skill

Invoke this skill when users ask about:

• Past work: "What did we do last session?"
• Bug fixes: "Did we fix this before?" or "What bugs did we fix?"
• Features: "How did we implement authentication?"
• Decisions: "Why did we choose this approach?"
• Code changes: "What files were modified in that refactor?"
• File history: "What changes to auth/login.ts?"
• Timeline context: "What was happening around that time?"
• Recent activity: "What have we been working on?"

Do NOT invoke for current session work or future planning (use regular tools for that).

Quick Decision Guide

Once the skill is loaded, choose the appropriate operation:

What are you looking for?

• "What did we do last session?" → operations/recent-context.md
• "Did we fix this bug before?" → operations/by-type.md (type=bugfix)
• "How did we implement X?" → operations/observations.md
• "What changes to file.ts?" → operations/by-file.md
• "What was happening then?" → operations/timeline.md
• "Why did we choose X?" → operations/observations.md (search for decisions)

Available Operations

Choose the appropriate operation file for detailed instructions:

Full-Text Search

1. Search Observations - Find observations by keyword (bugs, features, decisions, etc.)
2. Search Sessions - Search session summaries to understand what was accomplished
3. Search Prompts - Find what users have asked about in the past

Filtered Search

4. Search by Type - Find bugfix, feature, refactor, decision, or discovery observations
5. Search by Concept - Find observations tagged with specific concepts
6. Search by File - Find all work related to a specific file path

Context Retrieval

7. Get Recent Context - Get recent session summaries and observations for a project
8. Get Timeline - Get chronological timeline around a specific point in time
9. Timeline by Query - Search then get timeline around the best match

Utilities

10. API Help - Get API documentation

Common Workflows

For step-by-step guides on typical user requests, see operations/common-workflows.md:

• Understanding past work
• Finding specific bug fixes
• Understanding file history
• Timeline investigation

Response Formatting

For guidelines on how to present search results to users, see operations/formatting.md:

• Format=index responses (compact lists)
• Format=full responses (complete details)
• Timeline responses (chronologically grouped)

Technical Notes

• Port: Default 37777 (configurable via CLAUDE_MEM_WORKER_PORT)
• Response format: Always JSON
• Search type: FTS5 full-text search + structured filters
• All operations use HTTP GET with query parameters

Performance Tips

1. Use format=index first for overviews, then format=full for details
2. Start with limit=5-10, expand if needed
3. Use project filtering when working on one codebase
4. Use timeline depth of 5-10 for focused context
5. Be specific in search queries: "authentication JWT" > "auth"

Error Handling

If HTTP request fails:

1. Inform user the search service isn't available
2. Suggest checking if worker is running: pm2 list
3. Offer to help troubleshoot

For detailed error handling, see the specific operation files.