recall
- Repo stars 57
- Author updated Live
- Author repo joelclaw
- Domain
- AI · joelclaw · memory · recall
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 98 / 100 · audit passed
- Author / version / license
- @joelhooks · v1.0.0 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
---
name: recall
description: Fan-out search across all memory sources when context is unclear or vaguely referenced. Triggers…
category: ai
runtime: no special runtime
---
# recall output preview
## PART A: Task fit
- Use case: Fan-out search across all memory sources when context is unclear or vaguely referenced. Triggers on: 'from earlier', 'remember when', 'what we discussed', 'that thing with', 'the conversation about', 'did we ever', 'what happened with', 'you mentioned', 'we talked about', 'earlier today', 'last session', 'the other day', or any vague reference to past context that needs resolution before the agent can act..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Trigger Detection / Fan-Out Search Pattern / 1. Today's Daily Log (fastest, most likely)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Fan-out search across all memory sources when context is unclear or vaguely referenced. Triggers on: 'from earlier', 'remember when', 'what we discussed', 'that thing with', 'the conversation about', 'did we ever', 'what happened with', 'you mentioned', 'we talked about', 'earlier today', 'last session', 'the other day', or any vague reference to past context that needs resolution before the agent can act.”.
- **02** When the source has headings, the agent prioritizes “Trigger Detection / Fan-Out Search Pattern / 1. Today's Daily Log (fastest, most likely)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/tmp`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Trigger Detection / Fan-Out Search Pattern / 1. Today's Daily Log (fastest, most likely)”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: recall
description: Fan-out search across all memory sources when context is unclear or vaguely referenced. Triggers…
category: ai
source: joelhooks/joelclaw
---
# recall
## When to use
- Fan-out search across all memory sources when context is unclear or vaguely referenced. Triggers on: 'from earlier', '…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Trigger Detection / Fan-Out Search Pattern / 1. Today's Daily Log (fastest, most likely)” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "recall" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Trigger Detection / Fan-Out Search Pattern / 1. Today's Daily Log (fastest, most likely)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Recall — Find What Was Said
When Joel references something vaguely, don't guess — fan out across all memory sources and find it.
Trigger Detection
Phrases that indicate a recall is needed (case-insensitive):
- "from earlier", "earlier today", "earlier this week"
- "remember when", "remember that", "you mentioned"
- "what we discussed", "what we talked about", "the conversation about"
- "that thing with", "the thing about", "what was that"
- "did we ever", "have we", "wasn't there"
- "last session", "the other day", "yesterday"
- "correlate with", "connect to what we"
- Any vague pronoun reference to past context ("those photos", "that idea", "the notes")
Key principle: If you'd have to guess what "earlier" or "that" refers to, you need recall.
Fan-Out Search Pattern
Search these sources in parallel where possible, with timeouts on each:
1. Today's Daily Log (fastest, most likely)
# Always check first — most "from earlier" references are same-day
cat ~/.joelclaw/workspace/memory/$(date +%Y-%m-%d).md2. Recent Daily Logs (if today's doesn't have it)
# Yesterday and day before
cat ~/.joelclaw/workspace/memory/$(date -v-1d +%Y-%m-%d).md
cat ~/.joelclaw/workspace/memory/$(date -v-2d +%Y-%m-%d).md3. Curated Memory
cat ~/.joelclaw/workspace/MEMORY.mdSearch for keywords from the vague reference.
4. Session Transcripts
Use the session_context tool to search recent sessions:
sessions(limit: 10) # find recent session IDs
session_context(session_id: "...", query: "what was discussed about <topic>")5. Vault Notes
# Keyword search across Vault
grep -ri "<keywords>" ~/Vault/ --include="*.md" -l | head -106. System Log
slog tail --count 20 # recent infrastructure changes7. Processed Media
# Check for images/audio that were processed
ls /tmp/joelclaw-media/ 2>/dev/null8. Redis State
# Memory proposals, loop state, etc.
redis-cli LRANGE memory:review:pending 0 -1 2>/dev/nullWorkflow
- Extract keywords from the vague reference. "Those photos from earlier" → keywords: photos, images, media, telegram.
- Fan out across sources 1-8 above. Use
timeout 5on any command that might hang. - Synthesize — combine findings into a coherent summary of what was found.
- Present context — show Joel what you found, then continue with the original task.
- If nothing found — say so honestly. Don't fabricate. Ask Joel to clarify.
Timeouts Are Mandatory
Every external call (Redis, grep over large dirs, session reads) MUST have a timeout. The gateway session cannot hang on a recall operation.
# Good
timeout 5 grep -ri "keyword" ~/Vault/ --include="*.md" -l | head -10
# Bad — can hang indefinitely
grep -ri "keyword" ~/Vault/ --include="*.md"Anti-Patterns
- Don't grep one file and call it done. The whole point is fan-out.
- Don't guess when recall fails. Say "I couldn't find it" and ask.
- Don't read entire session transcripts. Use
session_contextwith a focused query. - Don't skip media. Photos, audio, processed images in
/tmp/joelclaw-media/are often what "from earlier" refers to.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review