52 lines
1.9 KiB
Markdown
52 lines
1.9 KiB
Markdown
Use this skill for deep memory search and recall. Trigger if the user says "what did I say about...", "when did we discuss...", "find that conversation about...", "history of...", or asks about past information that needs multi-file search.
|
|
|
|
## Domain
|
|
|
|
Memory recall — recursive search across all memory files, cross-referencing observations, entities, and action items.
|
|
|
|
## Memory Files
|
|
|
|
Read on activation:
|
|
- `memory/hot-memory.md` (for context on what's currently relevant)
|
|
|
|
Search across:
|
|
- All `observations.md` files (personal, work domains, cog-meta)
|
|
- All `entities.md` files
|
|
- All `action-items.md` files
|
|
- All `hot-memory.md` files
|
|
- `memory/glacier/` (via index.md for targeted retrieval)
|
|
|
|
## Process
|
|
|
|
### Pass 1: Locate
|
|
|
|
- Extract keywords from the user's query (names, topics, dates, phrases)
|
|
- `Grep path="memory/" pattern="<keyword>"` for each keyword
|
|
- Note which files matched and how many hits
|
|
- If >10 files match, narrow by domain or add query terms
|
|
- If 0 matches, try synonyms or related terms
|
|
- Check `memory/glacier/index.md` for archived data matching the query
|
|
|
|
### Pass 2: Extract
|
|
|
|
- Read the top 3-5 most relevant files (by hit density and recency)
|
|
- Extract the specific passages that match the query
|
|
- Track the timeline: when did the topic first come up? How did it evolve?
|
|
|
|
### Pass 3: Synthesize
|
|
|
|
- Combine extracted passages into a coherent answer
|
|
- Present findings chronologically with dates
|
|
- If something seems incomplete, flag it:
|
|
> "Found references to X in observations but no entity entry — want me to create one?"
|
|
|
|
## Artifact Formats
|
|
|
|
**Search result**: `YYYY-MM-DD: <summary of what was found>`
|
|
**Memory gap**: `Gap: referenced but not in memory — <topic>`
|
|
**Timeline**: Chronological list of when a topic appeared and how it evolved
|
|
|
|
## Activation
|
|
|
|
Extract search terms from the user's query and begin Pass 1. Be thorough but concise in the synthesis — don't dump raw content.
|