agent-memory-systems

Retrieve relevant memories and contextual information for stateful agent responses.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill agent-memory-systems-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-memory-systems
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/agent-memory-systems
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill agent-memory-systems-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many agent failures that look like poor reasoning are actually memory retrieval errors: the agent cannot find or prioritise the right past interactions, documents, or facts. This Skill provides the architectural patterns and operational guidance needed to design retrieval-first memory systems so agents maintain coherent, stateful behaviour across sessions.

Core Features & Use Cases

  • Memory Type Architecture: Guidance for short-term (context window), working, episodic, semantic, procedural, and long-term stores and when to use each.
  • Retrieval & Storage Patterns: Chunking strategies, embedding quality management, vector store selection, metadata filtering, temporal scoring, and conflict detection.
  • Use Case: A customer-support assistant that finds the most relevant past tickets, product logs, and meeting notes to answer a follow-up question without re-asking the customer.

Quick Start

Ask the agent to "Retrieve the top 5 memory chunks about customer Acme from the last 12 months, rank them by relevance and recency, and summarise key action items."

Frequently Asked Questions about agent-memory-systems

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

FAQPage Schema
How do I build agent memory retrieval for conversational context across sessions?

Build agent memory retrieval by implementing short-term, episodic, and long-term stores using vector stores and metadata filters. This ensures stateful agent responses by retrieving relevant past interactions and documents to maintain coherent behavior across sessions.

What is the best way to rank retrieved memory chunks by relevance and recency?

Rank retrieved memory chunks by applying temporal scoring alongside vector similarity. This approach prioritizes recent and relevant contextual information, enabling coherent, stateful agent responses without re-asking users for background.

How does temporal scoring improve vector store memory retrieval for agents?

Temporal scoring improves vector store memory retrieval by factoring recency into relevance rankings. This prevents outdated information from overshadowing recent interactions, ensuring agents retrieve the most contextually appropriate memories for stateful responses.

When should I use different chunking strategies for agent memory systems?

Use different chunking strategies based on whether you need short-term context window data, episodic logs, or long-term semantic knowledge. Proper chunking manages embedding quality and ensures the agent retrieves coherent, stateful information from vector stores.

Can I use metadata filtering to detect conflicts in agent memory retrieval?

Yes, you can use metadata filtering alongside vector store queries to detect conflicts in agent memory retrieval. This ensures the agent retrieves the most accurate contextual information and avoids contradictory past interactions.

Why does my agent forget previous interactions in document-backed workflows?

Agents forget previous interactions in document-backed workflows due to memory retrieval errors. Implementing retrieval-first memory systems with proper embedding quality tracking and vector store selection helps agents find and prioritize the right past facts.