memory-systems

Design layered memory architectures for agents using vector stores and temporal knowledge graphs.

9|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill memory-systems-abdullahmalik17
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: memory-systems
Source: https://github.com/AbdullahMalik17/Hacathan_5/tree/main/.claude/skills/memory-systems
Command: npx skills add https://github.com/AbdullahMalik17/Hacathan_5 --skill memory-systems-abdullahmalik17

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, making it impossible to maintain entity consistency, learn from past interactions, or reason over accumulated knowledge across conversations. ## Core Features & Use Cases - Layered Memory Architecture: Design working, short-term, long-term, entity, and temporal memory layers matched to query requirements. - Graph-Based Memory: Implement knowledge graphs and temporal knowledge graphs that preserve relationships and validity periods for time-aware queries. - Memory Consolidation: Merge duplicate facts, update validity periods, and prevent unbounded memory growth. - Use Case: Build a support agent that remembers a customer's address history and answers "What was the user's address on January 15, 2024?" using temporal graph queries instead of re-asking. ## Quick Start Ask the agent to design a memory architecture for a multi-session assistant that must track entities and their changing attributes over time.

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?▼

Implement layered memory: working memory in the context window, short-term session storage, and long-term persistence via vector stores or knowledge graphs. Store facts with entity tags and timestamps, then retrieve relevant memories just-in-time for each task.

What is the difference between vector RAG and knowledge graph memory?▼

Vector RAG retrieves semantically similar documents but loses relationship structure between entities. Knowledge graphs explicitly model entities and relationships, enabling traversal queries like "what products did customers who bought X also buy" that vector stores cannot answer.

When should I use a temporal knowledge graph for agent memory?▼

Use temporal knowledge graphs when facts change over time and you need time-travel queries, such as reconstructing a user's address on a specific date. They add valid_from and valid_until timestamps to facts, preventing outdated information from conflicting with current data.

Why does vector store memory fail for relationship queries?▼

Vector stores embed facts as isolated chunks without preserving connections between entities. Similarity search can retrieve a directly stated fact but cannot traverse relationships, so multi-hop questions across entities return incomplete or wrong results.

How do I prevent agent memory from growing unbounded?▼

Run periodic memory consolidation: identify duplicate facts grouped by subject and predicate, merge related entries keeping the highest-confidence version, update validity periods, and archive obsolete facts. Trigger consolidation after significant accumulation or on a schedule.