recall
Scannednpx machina-cli add skill shane9coy/katana-agent/recall --openclawFiles (1)
SKILL.md
1.7 KB
Recall ā Retrieve Memories
When This Fires
- User types
/recallwith a query - User asks: "what did we work on yesterday?"
- User asks: "what do you know about me?"
- User asks: "what's the status of project X?"
- User asks: "do you remember when we..."
- User references a past session or project
How To Search
Determine what user is asking for
| Question type | Search where |
|---|---|
| "What do you know about me?" | ~/.katana/memory/core/user.md |
| "How should you behave?" | ~/.katana/memory/core/soul.md |
| "What did we work on?" / project status | ~/.katana/memory/work.md |
| "What skills do we have?" | ~/.katana/memory/skills/_index.md |
| Unclear | Search all files |
Search work.md
Entries are formatted as:
## YYYY-MM-DD ā project-tag
Summary of work done...
Filter by project tag, date, or keyword.
Search projects/
Check ~/.katana/memory/projects/{name}/sessions.md for project-specific history.
Full-text search
For broad queries, use grep across all .md files:
grep -r -i "search term" ~/.katana/memory/ --include="*.md"
Response Format
Present findings concisely:
š Found 3 entries for "redis":
1. 2026-02-19 ā redis-cache
Implemented connection pooling. Fixed deadlock in transaction handler.
2. 2026-02-15 ā redis-cache
Initial setup with Sentinel failover. Chose ioredis over node-redis.
3. 2026-02-10 ā api-gateway
Added Redis caching layer for auth tokens. 15ms ā 2ms latency improvement.
Source
git clone https://github.com/shane9coy/katana-agent/blob/main/templates/universal/skills/recall/SKILL.mdView on GitHub Overview
Recall searches and retrieves memories from past sessions, projects, and memory files. It is triggered by /recall or natural prompts like what did we work on or what do you know about me. It helps maintain continuity and context across conversations.
How This Skill Works
Recall maps your query to memory sources such as user.md, soul.md, work.md, and per project sessions. It can perform targeted lookups or full text searches and then returns concise results with dates and tags.
When to Use It
- You want the status or outcomes of a past project
- You ask what we worked on yesterday or last session
- You ask what the agent knows about you
- You reference a past session or project and need context
- You need to search memory files for broad facts about skills or projects
Quick Start
- Step 1: Type /recall followed by your query (e.g., /recall project status)
- Step 2: Read the concise results returned with dates and tags
- Step 3: Reference or cite the memory in your current task or decision
Best Practices
- Use precise keywords that map to a specific memory source (e.g., project tag, date, or keyword)
- Start with a targeted query to avoid unrelated results
- Include a project name or date to narrow results
- Validate retrieved items against dates and tags
- When uncertain, run a full-text grep to surface broader matches
Example Use Cases
- Found 2 memories for 'Apollo integration': 2026-03-01 ā Apollo-integration: Implemented CMS integration; 2026-02-20 ā Apollo-integration: Deployed feature flags
- Found 1 memory for 'what we worked on yesterday': 2026-03-07 ā api-gateway: Refactored auth flow
- Found 3 memories for 'project X': 2026-02-15 ā X: Initial plan; 2026-02-28 ā X: Deployment script; 2026-03-03 ā X: QA results
- Found 2 memories for 'you know me': 2026-01-10 ā user prefs: adjust tone; 2026-03-01 ā memory core: updated soul profile
- Found 1 memory for 'sessions.md': 2026-03-04 ā session 42: sprint planning notes
Frequently Asked Questions
Add this skill to your agents