Menu
Show, set, clear, or migrate memini namespace pins with provenance. Use when project memories resolve to the wrong namespace.
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.
Delete a specific memini memory safely. Use when the user asks to forget, remove, or permanently delete stored memory.
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 | namespace |
| description | Show, set, clear, or migrate memini namespace pins with provenance. Use when project memories resolve to the wrong namespace. |
Resolve this skill's directory and run:
"<skill-directory>/../../scripts/run.sh" "<skill-directory>/../../scripts/namespace.mjs" <arguments>
No arguments shows the namespace and provenance. A namespace argument pins this
project server-side; --clear removes its pin; --migrate migrates legacy
overrides. Pins require a reachable server and beat MEMINI_NAMESPACE.
After setting or clearing a pin, explain that hooks pick it up on their next
invocation. Codex MCP configuration is established for a thread, so tell the
user to start a new thread (or restart Codex) before using memory_* tools with
the new namespace.