Mem Recall
- 18 installs
- Updated August 4, 2026
- akunzai/agent-skills
mem-recall is a Claude Code skill that searches short-term agent memory in .memories/ and ~/.agents/memories/ for handoffs, candidate notes, and prior task state.
About
mem-recall searches an agent's short-term memory on demand, scanning project .memories/ and ~/.agents/memories/ for recent daily logs, candidate notes, and open handoffs. It uses grep to pull only matching lines so whole logs are not loaded into context. A developer uses it when resuming a task and needing prior state that AGENTS.md or CLAUDE.md did not auto-load.
- Searches short-term memory in project .memories/ and ~/.agents/memories/ for handoffs, candidates, and prior task state
- Uses grep to extract only matching lines instead of reading whole logs into context
- Surfaces open handoff files so an agent can resume prior work
Mem Recall by the numbers
- 18 all-time installs (skills.sh)
- Ranked #2,053 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
mem-recall capabilities & compatibility
- Capabilities
- memory promote · memory sync
- Works with
- github
- Use cases
- memory · research
- Pricing
- Free
What mem-recall says it does
Retrieves short-term context: recent daily logs, candidates, and open handoffs.
Use `grep` to extract matching lines — do not read whole daily logs or the entire `.memories/` directory into context.
npx skills add https://github.com/akunzai/agent-skills --skill mem-recallAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 18 |
|---|---|
| Last updated | August 4, 2026 |
| Repository | akunzai/agent-skills ↗ |
What it does
Search short-term agent memory for recent logs, candidates, and open handoffs when resuming a task.
Who is it for?
Recalling recent daily logs and open handoffs to resume a task
Skip if: Loading durable instructions already provided by AGENTS.md or CLAUDE.md
When should I use this skill?
You need short-term context not already loaded by AGENTS.md / CLAUDE.md
What you get
The relevant recent logs and open handoffs are surfaced so work can resume with prior context.
- Surfaced matching log lines
- List of open handoff files to resume
By the numbers
- searches 2 memory locations (project .memories/ and ~/.agents/memories/)
Files
mem-recall — On-Demand Memory Search
Retrieves short-term context: recent daily logs, candidates, and open handoffs. Durable instructions come from auto-loaded AGENTS.md / CLAUDE.md, so this skill stays focused on short-term memory.
How to recall
# Recent project daily logs
grep -rn "pattern" .memories/ 2>/dev/null
# Recent global daily logs
grep -rn "pattern" ~/.agents/memories/ 2>/dev/null
# Open handoffs to resume — one file per active task, newest creation day last
ls .memories/handoffs/ 2>/dev/null
# Legacy fallback: handoffs still embedded inline in older daily logs
grep -rln "\[Handoff" .memories ~/.agents/memories 2>/dev/nullGuidance
- In a cross-device setup, run
/mem-sync(pull) first so you read the freshest logs. - Scope by recency: read newest daily logs first and limit to recent days. Use
grepto extract matching lines — do not read whole daily logs or the entire.memories/directory into context. - Focus recall on short-term logs. Do not re-read
AGENTS.md/CLAUDE.mdjust because the skill is active; coding agents already load them as project instructions — open them only if the loaded copy looks incomplete or you need exact wording. - When resuming work, list the open handoff files under
.memories/handoffs/, surface the
relevant one, and confirm with the user before continuing (the mem-auto autopilot does this at session start).
- This fallback grep is the safety net for legacy handoffs. The one-time migration normally
clears them (tracked by the .memories/.handoff-migrated sentinel, so mem-auto does not re-scan every start), but a /mem-sync pull can still bring in inline [Handoff] blocks from a device that never migrated. If a daily log holds such blocks, surface them and suggest a one-off re-run of the migration (mem-auto → references/handoff-migration.md) so they move under .memories/handoffs/. Don't rely on ls .memories/handoffs/ alone — un-migrated handoffs never appear there.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kFAQ
Where does mem-recall look?
It searches project .memories/ and global ~/.agents/memories/ for recent daily logs, candidates, and open handoffs.
Does it read entire logs?
No, it uses grep to extract only matching lines and reads newest daily logs first rather than the whole directory.