From cortex
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to cortex proactively. Do NOT wait for the user to ask.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cortex:memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have access to Cortex, a persistent memory system with knowledge graph, importance scoring,
You have access to Cortex, a persistent memory system with knowledge graph, importance scoring, full-text search, revision history, and temporal tracking 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.
Core memory:
mem_save, mem_search, mem_context, mem_session_summarymem_get_observation, mem_suggest_topic_key, mem_updatemem_session_start, mem_session_end, mem_save_promptmem_stats, mem_delete, mem_timeline, mem_capture_passiveKnowledge graph (Cortex-exclusive):
mem_relate — create typed relationships between observationsmem_graph — traverse the knowledge graph from an observationmem_score — get/recalculate importance scoremem_archive — archive low-importance observationsmem_search_hybrid — FTS5 + vector search with RRF fusionCortex v0.2.1 additions:
mem_revision_history — structured revision snapshots for observations (track upsert evolution)mem_merge_projects — consolidate fragmented project name variants into one canonical nameTemporal tools (experimental):
temporal_create_edge, temporal_get_edges, temporal_get_relevant, temporal_create_snapshottemporal_record_operation, temporal_evaluate_quality, temporal_system_metricstemporal_health_check, temporal_evolution_path, temporal_fact_stateFallback: If tools are unexpectedly unavailable, trigger ToolSearch manually:
select:mcp__plugin_cortex_cortex__mem_save,mcp__plugin_cortex_cortex__mem_search,mcp__plugin_cortex_cortex__mem_context,mcp__plugin_cortex_cortex__mem_session_summary,mcp__plugin_cortex_cortex__mem_get_observation,mcp__plugin_cortex_cortex__mem_suggest_topic_key,mcp__plugin_cortex_cortex__mem_update,mcp__plugin_cortex_cortex__mem_session_start,mcp__plugin_cortex_cortex__mem_session_end,mcp__plugin_cortex_cortex__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 (upsert)mem_suggest_topic_key firstmem_updateAfter saving related observations, use mem_relate to connect them:
references — direct reference to another observationrelates_to — related topic or conceptfollows — sequential relationshipsupersedes — replaces an older observationcontradicts — conflicting informationUse mem_graph to explore connections: mem_graph(observation_id, depth=2)
When the user asks to recall something — any variation of "remember", "recall", "what did we do":
mem_context — checks recent session history (fast, cheap)mem_search with relevant keywords (FTS5 full-text search)mem_search_hybrid for FTS5 + vector combined searchmem_get_observation for full untruncated content (search returns 300-char previews only)Also search memory PROACTIVELY when:
mem_search with keywordsmem_revision_history(observation_id) — see how an observation evolved across topic_key upsertsmem_timeline(observation_id, before, after) — chronological context around an observationmem_merge_projects(from: "my_project,myproject", to: "my-project")mem_archive(observation_id) (soft-delete, still findable with include_archived)mem_delete(id, hard_delete: true) (admin only, irreversible)mem_stats() (total observations, sessions, top projects)Before ending a session or saying "done" / "listo", you MUST:
mem_session_summary with this structure:[What we were working on this session]
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 contentmem_context to recover additional context from previous sessionsDo not skip step 1. Without it, everything done before compaction is lost from memory.
npx claudepluginhub lleontor705/cortex --plugin cortexProactively saves decisions, conventions, bugs, discoveries, and preferences to persistent Engram memory across sessions using mem_save and related tools.
Searches and retrieves memories from Cortex persistent memory using WRRF retrieval. Use for past decisions, patterns, bugs, or architecture context.
PROACTIVELY query Forgetful MCP (mcp__forgetful__* tools) when starting work on any project, when user references past decisions or patterns, when implementing features that may have been solved before, or when needing context about preferences. Save important decisions, patterns, and architectural insights to memory.