recall

Searches memory files across projects using progressive-disclosure grep retrieval.

3|Updated Oct 28, 2020
One-click install
npx skills add https://github.com/k0d3x8its/dotfiles --skill recall-k0d3x8its
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recall
Source: https://github.com/k0d3x8its/dotfiles/tree/main/claude/.claude/skills/recall
Command: npx skills add https://github.com/k0d3x8its/dotfiles --skill recall-k0d3x8its

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finding past decisions, session notes, and stored facts across a growing memory system is slow and token-expensive when every search reads entire files. This Skill retrieves memory in cheap layers, showing compact index hits first and expanding only what you choose. ## Core Features & Use Cases - Layered Retrieval: Grep EPISODIC-INDEX.md and KNOWLEDGE.md for low-cost Layer-1 hits, then expand to surrounding context (L2) or full blocks (L3) only on request. - Scoped Search: Default scope covers the current project's .memory/ files and KNOWLEDGE.md; the --deep flag fans out across all ~/dev projects, archives, and scratchpad memory. - git-crypt Guard: Detects encrypted KNOWLEDGE.md files before grepping and reports them as locked instead of reading ciphertext. - Use Case: You remember deciding on a database schema weeks ago but not the details. Run /recall schema to get one-line index hits, then expand the relevant session block to recover the full decision context. ## Quick Start Ask the assistant to recall a past decision or fact by running /recall followed by your search query, adding --deep to search across all projects.

Frequently Asked Questions about recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search past Claude session notes and decisions?▼

Run /recall followed by your query to grep the project's EPISODIC-INDEX.md, SESSION-LOG.md headers, and KNOWLEDGE.md files. You get a compact hit list first, then reply with a hit number to expand the matching session block or knowledge context.

How to search memory across multiple projects at once?▼

Use /recall --deep with your query to fan out across every project under ~/dev that contains memory files. Deep mode stays at grep-only Layer 1, labels archive hits as [archived] and scratchpad hits as [scratch], and never auto-reads full logs.

Does recall work with git-crypt encrypted knowledge files?▼

Yes, it checks the first bytes of each KNOWLEDGE.md for the git-crypt signature before grepping. Locked files are skipped and reported as [locked: project-name] so ciphertext is never searched or displayed.

What is the difference between default and deep recall scope?▼

Default scope searches only the current project's .memory/ files plus local and global KNOWLEDGE.md. Deep scope adds all ~/dev projects, EPISODIC-ARCHIVE.md files, and per-machine scratchpad memory, while remaining grep-only until you pick a hit.

Why does recall not show full session logs immediately?▼

Full logs cost 500-2K tokens each, so recall enforces progressive disclosure: Layer 1 shows one-line index hits, Layer 2 shows surrounding context on request, and Layer 3 reads full blocks only when you explicitly ask with 'full <n>'.