Menu
Pin or unpin a memini memory while preserving its existing tags. Use when the user wants a memory in every briefing.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
Delete a specific memini memory safely. Use when the user asks to forget, remove, or permanently delete stored memory.
Show, set, clear, or migrate memini namespace pins with provenance. Use when project memories resolve to the wrong namespace.
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 | pin |
| description | Pin or unpin a memini memory while preserving its existing tags. Use when the user wants a memory in every briefing. |
Locate the memory with memory_get or memory_recall and copy its id and
namespace verbatim. Read its current tags: memory_update replaces rather than
merges the tag list.
To pin, call memory_update with the existing tags plus pinned, preserving
order and avoiding duplicates. To unpin, pass the existing tags minus pinned.
If several candidates match, ask the user which one. Report the updated memory.
Pins are exempt from retro-tiering demotion, but not confidence decay or the briefing token/item budget. Warn when the pinned set is becoming large.
