memory-systems

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

Updated May 18, 2026
One-click install
npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill memory-systems-fts-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-systems
Source: https://github.com/fts-pro/FTS-MMIS-AFRIKA/tree/main/.agent/skills/memory-systems
Command: npx skills add https://github.com/fts-pro/FTS-MMIS-AFRIKA --skill memory-systems-fts-pro

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 retrieval patterns to the right tool. - 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 logic. - Use Case: When building a support agent that must remember user preferences and past issues across conversations, use this Skill to choose between Mem0's managed vector memory and Zep's temporal knowledge graph, then prototype with the included IntegratedMemorySystem script. ## Quick Start Ask the agent to help you choose and implement a memory framework for persisting user preferences across sessions, for example by saying "implement long-term memory for my agent using Mem0 or Zep".

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, and retrieve just-in-time rather than preloading everything into context.

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

Choose Mem0 for fast time-to-production with managed infrastructure and multi-tenant support. Choose Zep/Graphiti when you need bi-temporal modeling and relationship reasoning. Choose Cognee for dense multi-layer semantic graphs with customizable ingestion pipelines and strong multi-hop benchmark results.

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 queries like "where did the user live in March 2024". It prevents stale facts from poisoning context by invalidating outdated relationships without discarding history.

Does a simple file system work for agent memory?▼

Yes, file-system memory works well for prototypes and simple agents. Letta's filesystem-based agents scored 74% on the LoCoMo benchmark, beating Mem0's specialized tooling at 68.5%, showing that reliable retrieval matters more than tool sophistication.

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

Stale results occur when facts lack temporal validity tracking, so outdated information persists alongside current state. Fix this by adding valid_from and valid_until timestamps, preferring the most recent fact on conflict, and running periodic consolidation that invalidates rather than deletes old entries.

How do I benchmark an agent memory system?▼

Evaluate against established benchmarks like 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 and memory growth in production.