Menu
Delete a specific memini memory safely. Use when the user asks to forget, remove, or permanently delete stored memory.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Import older Claude Code sessions into memini. Requires the local memini binary.
Run read-only memini store and namespace diagnostics. Requires the local memini binary.
Show, set, clear, or migrate memini namespace pins with provenance. Use when project memories resolve to the wrong namespace.
Pin or unpin a memini memory while preserving its existing tags. Use when the user wants a memory in every briefing.
Show memini connection health, effective settings, namespace provenance, and read set. Use for configuration or recall diagnostics.
Search memini for prior context, decisions, or facts relevant to the current task. Use this skill when the user asks "what do you know about X", "did we discuss Y before", or before starting work that may have prior context (a file edit, an architectural change, debugging a recurring issue). The MCP tool is `memory_recall` on the bundled `memini` server.
| name | forget |
| description | Delete a specific memini memory safely. Use when the user asks to forget, remove, or permanently delete stored memory. |
Find the target first with memory_get when given an id, or memory_recall
when given a description. Copy the returned namespace verbatim.
Before deletion, show the full memory content and obtain explicit user
confirmation. Never delete more than one memory per confirmation, and never
guess between multiple candidates. Only after confirmation call
memory_forget with the id and returned namespace.
Prefer memory_update when the fact is merely wrong or outdated because it
preserves history. After deletion, say that the memory is permanently removed
from memini and may still remain in the current chat transcript.
