AI Agent Memory Systems
Use when the user asks about agent memory, long-term memory across sessions, remembering user preferences, context window full, conversation summarization, episodic or semantic memory. Produces memory tiers, a store schema and write/retrieve/expiry policies with per-user isolation. Not for document RAG (use llm-rag-retrieval-internals) or vector DB operations (use data-vector-databases).
Install
npx skills add j4flmao/agent-skills --skill ai-agent-memory-systemsgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/ai/ai-agents/memory-systems ~/.claude/skills/ai-agent-memory-systemsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Agent Memory Systems
## Purpose
An LLM is stateless between calls; anything the agent "remembers" is either placed in the context window or retrieved into it. Memory design is therefore a set of policies: what stays verbatim in context, what gets compressed, what is persisted to external stores, how it is retrieved, and when it is updated or deleted. Bad memory design shows up as forgotten constraints, contradictory facts, and leaked data between users.
## Agent Protocol
### Trigger
"agent memory", "long-term memory", "remember across sessions", "context window full", "conversation summarization", "user profile memory", "episodic memory", "memory leaks between users".
### Input Context
- Session length and turn count; model context size.
- What must persist across sessions (preferences, facts, past task outcomes).
- Privacy/tenancy constraints and retention requirements.
- Existing storage (Postgres, Redis, vector DB).
### Output Artifact
Memory design: tiers, schemas, write/read/eviction policies, isolation and retention rules.
### Response Format
```
Working memory: pinned={...} window={n turns} compression={summary|drop}
Semantic store: {schema} retrieval={hybrid+rerank} k={n}
Episodic store: {schema} written on={event}
Profile/facts: {key-value schema} update={upsert w/ provenance}
Isolation: {tenant/user key} Retention: {ttl} Deletion: {API}
```
### Completion Criteria
- [ ] Pinned context (instructions, goal, constraints) never evicted.Details
- Skill name
ai-agent-memory-systems- Repository
- j4flmao/agent-skills
- Path
skills/ai/ai-agents/memory-systems/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the AI Agent Memory Systems skill do?
Use when the user asks about agent memory, long-term memory across sessions, remembering user preferences, context window full, conversation summarization, episodic or semantic memory. Produces memory tiers, a store schema and write/retrieve/expiry policies with per-user isolation. Not for document RAG (use llm-rag-retrieval-internals) or vector DB operations (use data-vector-databases).
How do I install the AI Agent Memory Systems skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill ai-agent-memory-systems. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is AI Agent Memory Systems popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
AI Agentic Workflows
45j4flmao/agent-skills
Use when the user asks about an agentic workflow, prompt chaining, router, orchestrator-workers, evaluator-optimizer, ReAct, plan-and-execute or a LangGraph workflow with human checkpoints. Produces the simplest workflow pattern with typed state, loop bounds and approval points. Not for multi-agent runtimes (use ai-multi-agent-systems) or single-loop mechanics (use ai-agent-core-loop).
AI Multi Agent Systems
45j4flmao/agent-skills
Use when the user asks about a multi-agent system in LangGraph, AutoGen, CrewAI or OpenAI Agents SDK handoffs, shared blackboard state, A2A, checkpointing or human approval in an agent graph. Produces a runtime design: typed state, nodes, routing, durable checkpointer, interrupts, budgets and tracing. Not for choosing the topology (use multi-agent-topology).
Data Data Lakehouse
45j4flmao/agent-skills
Use when the user asks about lakehouse architecture, choosing Iceberg or Delta for our lakehouse, medallion bronze/silver/gold layers, Databricks Unity Catalog, Delta Sharing, Apache Paimon or multi-engine catalogs (Polaris, Glue). Produces layer design, catalog and access model and format commitment. Not for single-table operations (use data-data-lake).
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.