Agent skill · research science · aiskillstore
memory-systems
This skill should be used for persistent semantic memory in agent systems: cross-session knowledge retention, entity tracking, temporal validity, graph or vector retrieval, memory consolidation, and memory benchmark selection. Route file-backed scratchpads to filesystem-context, handoff summaries to context-compression, and token-efficiency tactics to context-optimization.
Why this skill is useful
Provides detailed architectural guidance on implementing layered memory systems, including knowledge graphs and temporal structures that the AI wouldn't reliably generate on its own.
What it needs
About 9k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Memory System Design Memory provides the persistence layer that allows agents to maintain continuity across sessions and reason over accumulated knowledge. Simple agents rely entirely on context for memory, losing all state when sessions end. Sophisticated agents implement layered memory architectures that balance immediate context needs with long-term knowledge retention. The evolution from vector stores to knowledge graphs to temporal knowledge graphs represents increasing investment in structured memory for improved retrieval and reasoning. When to Activate Activate this skill when: Building agents that must persist knowledge across sessions Choosing between memory frameworks (Mem0, Zep/Graphiti, Letta, LangMem, Cognee) Needing to maintain entity consistency across conversations Implementing reasoning over accumulated knowledge Designing memory architectures that scale in production Evaluating memory systems against benchmarks (LoCoMo, LongMemEval, DMR) Building dynamic memory with automatic entity/relationship extraction and self-improving memory (Cognee) Do not activate this skill for adjacent work owned by other skills: File-backed scratchpads, run logs, and tool-output offloading: filesystem-context. Conversation compaction or human-readable handoff summaries: context-compression. Masking, prefix caching, token budgets, or retrieval scoping inside one trajectory: context-optimization. Formal belief/desire/intention models over RDF state: bdi-mental-states. Core Concepts Think of memory as a spectrum from volatile context window to persistent storage. Default to the simplest layer that meets retrieval needs, because benchmark evidence suggests tool complexity matters less than reliable retrieval for some memory workloads (claim-memory-locomo-filesystem-baseline). Add structure (graphs, temporal validity) only when retrieval quality degrades or the agent needs multi-hop reasoning, relationship traversal, or time-travel queries. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/memory-systems--a20c13