Proactively saves decisions, conventions, bugs, discoveries, and preferences to persistent Engram memory across sessions using mem_save and related tools.
From engramnpx claudepluginhub gentleman-programming/engram --plugin engramThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.
You have access to Engram, a persistent memory system that survives across sessions and compactions. This protocol is MANDATORY and ALWAYS ACTIVE — not something you activate on demand.
Core tools are loaded automatically at session start by the UserPromptSubmit hook. They are available immediately — no manual ToolSearch needed.
mem_save, mem_search, mem_context, mem_session_summarymem_get_observation, mem_suggest_topic_key, mem_updatemem_session_start, mem_session_end, mem_save_promptFallback: If tools are unexpectedly unavailable, trigger ToolSearch manually:
select:mcp__plugin_engram_engram__mem_save,mcp__plugin_engram_engram__mem_search,mcp__plugin_engram_engram__mem_context,mcp__plugin_engram_engram__mem_session_summary,mcp__plugin_engram_engram__mem_get_observation,mcp__plugin_engram_engram__mem_suggest_topic_key,mcp__plugin_engram_engram__mem_update,mcp__plugin_engram_engram__mem_session_start,mcp__plugin_engram_engram__mem_session_end,mcp__plugin_engram_engram__mem_save_prompt
Admin tools (deferred — use ToolSearch only if needed):
mem_stats, mem_delete, mem_timeline, mem_capture_passiveCall mem_save IMMEDIATELY and WITHOUT BEING ASKED after any of these:
"Did I or the user just make a decision, confirm a recommendation, express a preference, fix a bug, learn something non-obvious, or establish a convention? If yes, call mem_save NOW."
Format for mem_save:
project (default) | personalarchitecture/auth-modelmem_save with the same topic_key so memory is updated (upsert) instead of creating a new observationmem_suggest_topic_key first, then reuse that key consistentlymem_updateWhen the user asks to recall something — any variation of "remember", "recall", "what did we do", "how did we solve", "recordar", "acordate", "qué hicimos", or references to past work:
mem_context — checks recent session history (fast, cheap)mem_search with relevant keywords (FTS5 full-text search)mem_get_observation for full untruncated contentAlso search memory PROACTIVELY when:
mem_search with keywords from their message to check for prior work before respondingBefore ending a session or saying "done" / "listo" / "that's it", you MUST:
mem_session_summary with this structure:[What we were working on this session]
[User preferences or constraints discovered — skip if none]
This is NOT optional. If you skip this, the next session starts blind.
If you see a message about compaction or context reset:
mem_session_summary with the compacted summary content — this persists what was done before compactionmem_context to recover any additional context from previous sessionsDo not skip step 1. Without it, everything done before compaction is lost from memory. All core tools are loaded automatically by the hook at session start — use the fallback ToolSearch above if they are unexpectedly missing.