Recall Search
Scannednpx machina-cli add skill davegoldblatt/total-recall/recall-search --openclawSearch across all memory tiers for relevant information.
Query: $ARGUMENTS
Search Protocol
Search in this order (narrow to wide):
1. Working Memory (CLAUDE.local.md)
Already loaded — check if the answer is here first.
2. Registers (memory/registers/*.md)
Search all register files for content matching the query:
- people.md
- projects.md
- decisions.md
- preferences.md
- tech-stack.md
- open-loops.md
- Any other .md files in registers/
3. Recent Daily Logs (memory/daily/)
Search the last 14 days of daily logs. Start with most recent.
4. Archive (memory/archive/)
Only search here if nothing found in tiers 1-3, or if the query explicitly asks about historical/past items.
How to Search
Use grep/ripgrep across the memory directory for matching content. This is keyword/pattern matching — search for relevant terms, synonyms, and related phrases.
Output Format
Present results grouped by source, most relevant first:
Found [N] relevant entries:
[registers/decisions.md] (confidence: high)
2026-01-15: Chose JWT over session cookies for stateless scaling
[registers/tech-stack.md] (confidence: high)
Auth: JWT tokens with 24h expiry, refresh via /auth/refresh
[daily/2026-02-01.md]
[14:32] Discussed adding OAuth2 for third-party integrations, decided to defer
If Nothing Found
Tell the user:
No matching entries found in memory.
Searched: CLAUDE.local.md, [N] registers, [N] daily logs, [N] archive files.
Suggest they use /recall-write to capture the information if they have it.
Important
- Show the actual content, not just file names
- Include confidence levels when available on register entries
- Show dates and timestamps for daily log entries
- If a result is marked
[superseded], note that and show the current entry instead - Do NOT fabricate results — only return what's actually in the files
Source
git clone https://github.com/davegoldblatt/total-recall/blob/main/skills/recall-search/SKILL.mdView on GitHub Overview
Recall Search scans CLAUDE.local.md, registers, recent daily logs, and the archive to find relevant information. It uses grep/ripgrep-style keyword matching and presents results grouped by source with confidence where available. This helps surface context and decisions quickly without manual digging.
How This Skill Works
Provide a query; the system searches in this order: Working Memory (CLAUDE.local.md), Registers (memory/registers/*.md), Recent Daily Logs (memory/daily/, last 14 days), then Archive (memory/archive/). It uses keyword matching to locate terms and related phrases, and outputs results grouped by source with dates, timestamps, and confidence when present.
When to Use It
- You need to recall a past decision or rationale stored in registers (e.g., decisions.md, tech-stack.md).
- You want a recent note about a project from daily logs to refresh context.
- You must verify consistency of information across memory tiers before acting.
- You’re researching historical context not present in working memory (CLAUDE.local.md).
- You need to gather multiple mentions of a term across memory to inform a change.
Quick Start
- Step 1: Enter your query for the information you need.
- Step 2: Run recall search; review results grouped by source with confidence.
- Step 3: Validate findings by cross-checking multiple sources before acting.
Best Practices
- Start with CLAUDE.local.md to check working memory first.
- Use precise keywords and synonyms; try different phrasings for completeness.
- Limit or constrain searches by date when inspecting daily logs (last 14 days).
- Pay attention to confidence levels and any [superseded] notes.
- If nothing is found, avoid fabricating results—use the no-match message and consider /recall-write to capture new info.
Example Use Cases
- Found a high-confidence entry in registers/decisions.md about choosing JWT over session cookies for stateless scaling.
- Located an authentication approach note in registers/tech-stack.md indicating JWT tokens with 24h expiry.
- Retrieved a recent daily log entry from memory/daily/2026-02-01.md mentioning deferring OAuth2 integration.
- Discovered a superseded entry and identified the current replacement in the relevant register file.
- No matching entries found; system returned a standardized no-results message and suggested using /recall-write.
