# Design Reliable Agent Memory Systems

Agent memory designs often add complexity without improving retrieval quality. This skill guides architecture choices and provides practical vector, graph, and temporal prototypes.

## Install

```bash
npx skillstore add muratcankoylan/memory-systems
```

## Metadata

- Status: approved
- Slug: muratcankoylan-memory-systems
- Skillstore revision: r2
- Version status: missing
- Tree hash: c05a22a77b9d1c78371855a012c5f6d2486273e81426ee501687778e2ce104f3
- Author: muratcankoylan
- GitHub username: muratcankoylan
- License: MIT
- Repository: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/memory-systems
- Ref: 02be9409c79ca1183f7844009c14d9df684d0cf9
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 72
- Public page: https://skillstore.pages.dev/skills/muratcankoylan-memory-systems
- Manifest: https://skillstore.pages.dev/api/skills/muratcankoylan-memory-systems/manifest

## Capabilities

- Compares Mem0, Graphiti, Letta, Cognee, LangMem, and file-based memory by retrieval needs.
- Maps working, short-term, long-term, entity, and temporal memory layers to practical requirements.
- Provides an in-memory vector store with metadata, entity, time, and session filters.
- Provides property graph and temporal relationship structures for entity and point-in-time queries.
- Combines vector retrieval with graph relationship context through one prototype interface.
- Explains consolidation triggers, benchmark selection, failure recovery, and framework trade-offs.

## Use Cases

- Select a Memory Architecture: Compare storage layers and frameworks against retrieval shape, temporal needs, operational cost, and expected scale.
- Prototype Structured Retrieval: Build a local proof of concept using entity metadata, graph relationships, session filters, and temporal validity.
- Plan Memory Evaluation: Choose benchmarks, define retrieval failure handling, and measure quality before adopting more complex infrastructure.

## Prompt Templates

### Choose a Starting Layer

```
Recommend the simplest memory layer for an agent that must remember [information] across [duration]. Explain storage, retrieval, and failure handling.
```

### Compare Memory Frameworks

```
Compare Mem0, Graphiti, Letta, Cognee, and file storage for [use case]. Prioritize retrieval quality, temporal reasoning, cost, and operations.
```

### Design a Temporal Schema

```
Design an entity and relationship model for [domain]. Include validity periods, conflict handling, provenance, deletion, and example time-scoped queries.
```

### Create a Migration and Benchmark Plan

```
Plan migration from [current store] to [target architecture]. Define data conversion, rollback, privacy controls, LoCoMo or LongMemEval tests, and acceptance thresholds.
```

## Limitations

- The included Python store is in-memory and does not persist data across process restarts.
- Its deterministic pseudo-embeddings demonstrate interfaces but do not provide real semantic retrieval.
- The consolidation method is a placeholder and requires a production implementation.
- Third-party examples require separate dependencies, infrastructure, access controls, and privacy policies.

## Best Practices

- Start with the shallowest persistent layer that meets measured retrieval needs.
- Track validity, provenance, retention, and deletion requirements for every changeable fact.
- Treat retrieved memory as untrusted data and test resistance to stale, conflicting, or malicious content.

## Anti Patterns

- Do not load every stored memory into the active context.
- Do not claim semantic quality from the included pseudo-embedding prototype.
- Do not deploy persistent personal memory without access controls, retention limits, and deletion workflows.

## Security Audit

- Audited at: 2026-08-09T09:48:13.116\+00:00
- Summary: All 55 static findings are false positives caused by Markdown backticks, code fences, ordinary graph identifiers, and a documentation link. No shell execution, system reconnaissance, or outbound request logic was found, but the reference context formatter inserts stored memory text without prompt-injection safeguards.

## Stats

- Views: 180
- Downloads: 13
- Favorites: 0
- Popularity score: 0