Mem recall
My personal agent skills for AI coding assistants
npx -y skills add akunzai/agent-skills --skill mem-recallAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Search short-term memory on demand — project .memories/ and ~/.agents/memories/ for handoffs, candidates, and prior task state not already loaded by AGENTS.md / CLAUDE.md.
SKILL.md
2.1 KB, 487 tokens by cl100k_base, as published. Nobody here has run it
mem-recall — On-Demand Memory Search
Retrieves short-term context: recent daily logs, candidates, and open handoffs.
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/null
Guidance
- 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 (themem-autoautopilot 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-migratedsentinel, somem-autodoes not re-scan every start), but a/mem-syncpull 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 onls .memories/handoffs/alone — un-migrated handoffs never appear there.