memory-systems

Store and retrieve structured memories with vector and graph search.

Updated May 24, 2026
One-click install
npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill memory-systems-fvossebeld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-systems
Source: https://github.com/FVossebeld/agent-skills-for-context-engineering/tree/main/skills/memory-systems
Command: npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill memory-systems-fvossebeld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a unified memory layer enabling persistent semantic memory across sessions, entity tracking, and efficient retrieval for long-running agents.

Core Features & Use Cases

  • Persistent semantic memory across conversations
  • Entity tracking and temporal reasoning with graph and temporal knowledge graphs
  • Hybrid retrieval combining vector search and graph context
  • Consolidation and memory management

Quick Start

Store a memory for an entity and retrieve memories across sessions to maintain continuity.

Frequently Asked Questions about memory-systems

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

FAQPage Schema
How do I persist agent memory across sessions for continuity?

Cross-session memory persistence is achieved by storing structured memories that support vector-based semantic search and graph-based entity relationships. This enables continuity for long-running agents by loading context just-in-time across conversations.

How does hybrid retrieval combine vector search and graph context?

Hybrid retrieval combines vector-based semantic search with graph-based entity relationships to provide comprehensive context. This approach allows agents to query both unstructured semantic similarities and structured temporal knowledge graph connections simultaneously.

Can I use numpy to manage temporal knowledge graphs for entity tracking?

Numpy is the required dependency for managing temporal knowledge graphs and entity tracking. It handles the numerical operations underlying the vector-based semantic search and structured memory consolidation processes across sessions.

What is the best way to answer time-bound queries using a temporal knowledge graph?

Answering time-bound queries requires a temporal knowledge graph that tracks entity validity over time. This enables agents to retrieve historically accurate context and consolidate memories based on temporal provenance tracking.

Does memory consolidation and provenance tracking work with property graphs?

Memory consolidation and provenance tracking integrate directly with property graphs by storing structured memories with graph-based entity relationships. This integration supports efficient retrieval and temporal reasoning across persistent sessions.

When do I need just-in-time loading for persistent semantic memory?

Just-in-time loading is needed when long-running agents require efficient retrieval of persistent semantic memory without loading entire histories. It optimizes cross-session continuity by fetching specific vector and graph contexts on demand.