memory-systems

Designs agent memory architectures using vector stores, knowledge graphs, and temporal retrieval frameworks.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/whatswithavi/Ecchelon_project --skill memory-systems-whatswithavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-systems
Source: https://github.com/whatswithavi/Ecchelon_project/tree/main/.agent/skills/memory-systems
Command: npx skills add https://github.com/whatswithavi/Ecchelon_project --skill memory-systems-whatswithavi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, and includes scripts (resource) and references (resource) components.

What problem does it solve? Agents lose all state when sessions end, forcing users to repeat context and preventing long-term knowledge accumulation. This Skill guides the design of persistence architectures that retain facts, entities, and relationships across sessions with reliable retrieval. ## Core Features & Use Cases - Framework Selection: Compares production memory frameworks (Mem0, Zep/Graphiti, Letta, LangMem, Cognee) with benchmark data from LoCoMo, LongMemEval, DMR, and HotPotQA to match frameworks to retrieval patterns. - Layered Memory Design: Provides decision tables for working, short-term, long-term, entity, and temporal knowledge graph layers so you add complexity only when retrieval quality demands it. - Reference Implementations: Ships Python building blocks for vector stores with metadata indexing, property graphs with entity registries, temporal knowledge graphs with validity intervals, and memory consolidation. - Use Case: You are building a support agent that must remember user preferences and past issues across conversations. Use this Skill to choose between Mem0 and Zep, implement temporal validity tracking, and set up consolidation triggers. ## Quick Start Ask the agent to design a memory architecture for a chatbot that must remember user preferences across sessions and recommend a framework.

Frequently Asked Questions about memory-systems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add long-term memory to an AI agent?▼

Start with file-system memory storing facts as structured JSON with timestamps, then escalate to a vector store like Mem0 when you need semantic search. Add a temporal knowledge graph such as Zep/Graphiti only when the agent needs relationship traversal or time-travel queries.

Mem0 vs Zep vs Cognee: which agent memory framework should I choose?▼

Choose Mem0 for fast time-to-production with managed infrastructure, Zep/Graphiti for bi-temporal modeling and relationship reasoning, and Cognee for dense multi-layer semantic graphs with customizable ingestion pipelines. Letta fits agents needing deep self-introspection over their own memory.

What is a temporal knowledge graph for agent memory?▼

A temporal knowledge graph stores facts with valid_from and valid_until timestamps so agents can answer point-in-time queries like where a user lived in March 2024. It prevents stale facts from poisoning context by tracking when information stops being true.

Does a simple file system work for agent memory?▼

Yes, benchmark evidence shows Letta's filesystem agents scored 74% on LoCoMo using basic file operations, beating Mem0's specialized tools at 68.5%. Reliable retrieval matters more than tool sophistication for many use cases.

Why does agent memory retrieval degrade over time?▼

Unbounded memory growth and stale facts that contradict current state degrade retrieval quality. Run periodic consolidation triggered by memory count thresholds, invalidate rather than discard outdated facts, and pin a single embedding model per store.

How do I benchmark an agent memory system?▼

Evaluate against LoCoMo for long-conversation retention, LongMemEval for long-term memory, and HotPotQA for multi-hop reasoning. Treat benchmarks as signals for specific retrieval dimensions rather than absolute rankings, and measure before and after architecture changes.