memory-systems

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

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/ludotype/game-adventurertown --skill memory-systems-ludotype
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-systems
Source: https://github.com/ludotype/game-adventurertown/tree/main/.agent/skills/memory-systems
Command: npx skills add https://github.com/ludotype/game-adventurertown --skill memory-systems-ludotype

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 layered memory architectures that persist 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 Architecture Guidance: Provides decision tables for working, short-term, long-term, entity, and temporal knowledge graph memory layers, plus retrieval strategies (semantic, entity-based, temporal, hybrid). - Runnable Implementation: Ships a Python module with VectorStore, PropertyGraph, TemporalKnowledgeGraph, and an IntegratedMemorySystem for prototyping before committing to infrastructure. - Use Case: When building a support agent that must remember user preferences and track changing facts (e.g., addresses, subscriptions) across months of conversations, use this Skill to choose a framework, design temporal validity tracking, and prototype the storage layer. ## Quick Start Ask the agent to design a memory architecture for a chatbot that must remember user preferences across sessions and recommend whether to use Mem0, Zep, or a simple file-based store.

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 the simplest layer that meets your retrieval needs: file-system storage for prototypes, then a vector store like Mem0 for semantic search, and a temporal knowledge graph like Zep/Graphiti only when you need relationship traversal or time-scoped queries. Store facts with entity and timestamp metadata from the beginning.

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 as relationships with valid_from and valid_until timestamps, letting agents answer point-in-time questions like where a user lived in March 2024. It prevents stale facts from poisoning context by invalidating rather than deleting outdated information.

Does a simple file system work for agent memory?▼

Yes, benchmark evidence shows Letta's filesystem-based agents scored 74% on LoCoMo using basic file operations, beating Mem0's specialized tools at 68.5%. Reliable retrieval matters more than tool sophistication, so prototype with files before adding infrastructure.

Why does agent memory retrieval return stale or conflicting facts?▼

Stale results occur when facts lack temporal validity tracking, so outdated entries poison the context. Check valid_until timestamps, prefer facts with the most recent valid_from, and trigger consolidation when retrieval quality degrades.

How do I benchmark an agent memory system?▼

Evaluate against LoCoMo for long-conversation retention, LongMemEval for long-term memory accuracy, DMR for dialogue memory, and HotPotQA for multi-hop reasoning. Benchmark before and after architectural changes, and monitor retrieval latency in production.