V3 Memory Unification

Consolidates multiple memory backends into AgentDB with HNSW vector search indexing.

1|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/KentwareDemo/RuView --skill v3-memory-unification-kentwaredemo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: V3 Memory Unification
Source: https://github.com/KentwareDemo/RuView/tree/main/.claude/skills/v3-memory-unification
Command: npx skills add https://github.com/KentwareDemo/RuView --skill v3-memory-unification-kentwaredemo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fragmented memory systems across agents (SQLite, Markdown, swarm memory, distributed stores) cause slow queries, duplicated data, and no cross-agent sharing. This Skill unifies them into a single AgentDB backend with HNSW vector indexing for fast semantic search. ## Core Features & Use Cases - Unified Memory Service: Implements a single IMemoryBackend interface routing semantic queries to HNSW search and structured queries to AgentDB. - Data Migration: Migrates entries from SQLite backends and Markdown files into AgentDB with generated embeddings. - SONA Integration: Stores and retrieves learning patterns with reward and adaptation metadata for self-learning agents. - Use Case: An agent platform running seven separate memory stores migrates all entries into AgentDB, then serves sub-100ms semantic queries across one million entries while sharing memory between agents. ## Quick Start Ask the agent to design an AgentDB unification strategy and migrate the existing SQLite and Markdown memory stores into a single HNSW-indexed backend.

Frequently Asked Questions about V3 Memory Unification

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

FAQPage Schema
How do I migrate SQLite memory data to AgentDB?

Read all entries from the SQLite backend, generate an embedding for each entry's content, then store the entry with its embedding in AgentDB. The same pattern applies to Markdown files by reading file content and preserving the original path in metadata.

What is HNSW indexing used for in vector search?

HNSW (Hierarchical Navigable Small World) is an approximate nearest-neighbor index that accelerates semantic similarity search over embeddings. This Skill configures it with parameters like efConstruction 200 and M 16 to target large search speedups over brute-force queries.

Does AgentDB support cross-agent memory sharing?

Yes, the unified memory service is designed for real-time cross-agent memory synchronization. Once legacy per-agent stores like SwarmMemory are migrated, all agents query the same AgentDB backend through the shared interface.

How does SONA learning integrate with the memory backend?

Learning patterns are stored as memory entries whose metadata includes the SONA mode, reward, and adaptation time, along with a content embedding. Similar patterns are retrieved through semantic queries filtered by the learning pattern type.

What are the limitations of HNSW vector search?

HNSW trades exact results for speed, so approximate search may miss some true nearest neighbors depending on index parameters. It also requires generating embeddings for every stored entry, adding upfront migration and storage cost.