Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated decisions, incorrect memories, sensitive data, or cleaning up after experiments. Also handles undo of recent additions.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Delete specific memories from mem0.
The user provides either:
/mem0:forget auth module decisions/mem0:forget <memory_id>If no argument, ask: "What should I forget? Provide a search query or memory ID."
If memory ID provided (looks like a UUID or hex string):
get_memory with the ID to verify it exists.Found: "<memory content first 120 chars>" (created <date>)If search query provided:
search_memories with:
query=<user's query>filters={"AND": [{"user_id": "<active_user_id>"}, {"app_id": "<project_id>"}]}top_k=10Found <N> memories matching "<query>":
1. <content, 120 chars> (type: <type>, created: <date>) [ID: <short_id>]
2. ...Ask: "Delete which memories? Enter numbers (e.g., 1,3,5), 'all', or 'cancel'."
For a single memory ID, ask: "Delete this memory? [y/N]"
Never delete without confirmation. This is destructive.
For each confirmed memory, call delete_memory with the memory ID.
Deleted <N> memories.If any deletions failed, report which ones and why.
If the user says "undo last N memories" or "undo last write":
SCRIPT_DIR="${CLAUDE_PLUGIN_ROOT:-${CODEX_PLUGIN_ROOT:-${CURSOR_PLUGIN_ROOT:-}}}/scripts"
python3 "$SCRIPT_DIR/session_stats.py" peekrecent_ids array from the JSON output. Each entry has id, category, ts.delete_memory.If recent_ids is empty, tell the user: "No recent memory IDs tracked this session. Try /mem0:tour to browse recent memories, or /mem0:forget <search query> to find specific ones."
b357a5a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.