Menu
Look up what Mneme knows about a file, function, or entity. Use when the user asks "what do you know about X", wants to check entity history, or asks about file/function activity and mentions.
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
Remove entries from remembered items. Use when the user wants to delete, remove, or clear a previously remembered item, or says "forget this", "remove that memory", or "clear my preferences".
Create a session briefing for the next session — auto-loaded, then archived. Use when the user is wrapping up a session, says "save this for next time", "hand off", "brief the next session", or wants to ensure continuity before stopping work.
Inject filtered context from previous sessions. Use when the user says "recall", "what happened last session", "what did we work on", "inject previous context", or when you need context from a prior session to continue work. Also useful mid-session when the user references prior work you don't have context for.
Save something to memory for future sessions. Use when the user says "remember this", "save for later", "don't forget", or wants to persist any preference, fact, lesson, or note across sessions.
Check plugin health and diagnose issues. Use when the user asks about mneme health, memory status, plugin errors, wants to troubleshoot memory issues, or sees error warnings at session start.
Force immediate memory summarization. Use when the user wants to compress the activity log, trigger summarization manually, or says "summarize memory", "compress the log", or "update the summary".
| name | entity |
| description | Look up what Mneme knows about a file, function, or entity. Use when the user asks "what do you know about X", wants to check entity history, or asks about file/function activity and mentions. |
| argument-hint | [entity name] |
Query the entity index for files, functions, errors, or packages:
# Search by name (partial match)
node "${CLAUDE_PLUGIN_ROOT}/scripts/mem-entity.mjs" $ARGUMENTS
# List all entities (optionally filtered)
node "${CLAUDE_PLUGIN_ROOT}/scripts/mem-entity.mjs" --list [--category files|functions|errors|packages]
Returns JSON with matches[]: each has name, category, mentions, lastSeen, contexts.
If no query provided, ask the user what entity to look up.