recall
SolidSearch memories and decisions to answer questions about past learnings, choices, and context
Install
Quality Score: 83/100
Skill Content
Details
- Author
- jmylchreest
- Repository
- jmylchreest/aide
- Created
- 5 months ago
- Last Updated
- today
- Language
- Go
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
memory-search
Searches the project's recorded memory (core-memory-kit) — decisions, conventions, architecture, the reasoning behind choices, and where things live — and returns a curated, cited summary. Fire whenever the answer might be something the project already established in past work, HOWEVER the question is phrased — any prior decision, convention, rationale, or "how/where/why is it this way" question, including oblique or roundabout asks ("why is everything so spread out?", "remind me what we settled on for X", "how come these files are tiny?"). Also fire when a "[core-memory-kit] Memory available" hint appears on the prompt. The examples are illustrative, not a checklist — prefer recalling over re-deriving an answer from the code. The session-start snapshot is a bounded index; this skill reaches the rest. Skip only when the question is purely about uncommitted or just-edited live code that memory cannot know, concerns this conversation only, or the user asked to ignore memory.
recall
Query the recall knowledge base for relevant context. Searches decisions, patterns, gotchas, links, and insights stored across sessions. TRIGGER when: user asks to "recall", "remember", "what did we decide about", "check knowledge base", or references past decisions/patterns. DO NOT TRIGGER when: user is talking about memory/recall in a general sense, or working on the recall agent code itself.
cortex-recall
Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or architecture choices. Also use proactively when working on something that likely has relevant historical context.