Mem clean
My personal agent skills for AI coding assistants
npx -y skills add akunzai/agent-skills --skill mem-cleanAssembled 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
Interactively clean short-term memory — delete expired project/global daily logs (.memories/YYYY-MM-DD.md) under a confirmed retention plan, and resolve cloud-drive conflict copies. Destructive; always requires a dry-run plan and explicit user confirmation.
SKILL.md
1.6 KB, 340 tokens by cl100k_base, as published. Nobody here has run it
mem-clean — Short-Term Memory Cleanup
What it cleans
- Expired project logs in
<repo>/.memories/YYYY-MM-DD.md— see references/short-term-cleanup.md. - Expired global logs in
~/.agents/memories/YYYY-MM-DD.md— deleted directly (not git-synced; see the reference). - Cloud conflict copies (
*Conflict*/*conflicted*) in~/.agents/— see references/cloud-conflict-resolver.md.
Rules (summary)
- Default retention is 30 days, computed from the
YYYY-MM-DD.mdfilename, never mtime. - Block cleanup of daily logs with unresolved
[Candidate]entries (not[Promoted],[Rejected], or[Expired]). - Leave
.memories/handoffs/files alone: active handoffs are managed bymem-auto, which deletes each task's file on completion. Only offer to remove a handoff file when the user confirms its task is abandoned. - Project cleanup is per-user: after deleting expired logs locally, run
/mem-syncfirst, thenmem-sync-git.sh compactto rewrite the user'smemories/<email-localpart>branch to a single commit and force-push. Other devices adopt it on next pull. - Always show the dry-run plan (scope, retention window, delete list, blocked files, user keep-list) and require explicit confirmation.