V3 Memory Unification

Migrate legacy memory systems into AgentDB with HNSW vector indexing.

11|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ishandutta2007/claude-agent-orchestration --skill v3-memory-unification-ishandutta2007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: V3 Memory Unification
Source: https://github.com/ishandutta2007/claude-agent-orchestration/tree/main/.claude/skills/v3-memory-unification
Command: npx skills add https://github.com/ishandutta2007/claude-agent-orchestration --skill v3-memory-unification-ishandutta2007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fragmented memory backends (SQLite, Markdown, distributed stores) make agent memory slow and inconsistent. This Skill consolidates 7 legacy memory systems into a unified AgentDB backend with HNSW vector search, delivering 150x-12,500x faster semantic queries while preserving backward compatibility. ## Core Features & Use Cases - Unified Memory Service: Implements a single IMemoryBackend interface routing semantic queries through HNSW indexing and standard queries through AgentDB. - Data Migration Pipelines: Provides phased migration strategies for moving SQLite and Markdown memory stores into AgentDB with generated embeddings. - SONA Learning Integration: Stores and retrieves learning patterns with reward and adaptation metadata for cross-agent memory sharing. - Use Case: When upgrading a multi-agent orchestration system, use this Skill to consolidate scattered memory backends into one vector-indexed store, then validate the 150x-12,500x search speedup and 50-75% memory reduction targets. ## Quick Start Ask the agent to design an AgentDB unification strategy and migrate the existing SQLite and Markdown memory stores to HNSW-indexed vector search.

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 stores to AgentDB?

Migrate SQLite to AgentDB by reading all entries from the legacy store, generating an embedding for each entry's content, and storing the entry with its embedding in AgentDB. The Skill provides a phased migration script pattern for this process.

What is HNSW indexing and why use it for agent memory?

HNSW (Hierarchical Navigable Small World) is a graph-based approximate nearest neighbor index used for fast vector similarity search. In this Skill it targets 150x-12,500x search speedups over legacy memory backends with sub-100ms latency on 1M+ entries.

Does AgentDB unification keep backward compatibility with existing memory backends?

Yes, the unified memory service implements the IMemoryBackend interface so existing callers continue working. Semantic queries route through the HNSW indexer while standard queries go directly to AgentDB.

How does SONA learning integrate with the unified memory store?

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

What are the limitations of HNSW vector search for memory?

HNSW requires generating embeddings for every stored entry, adding indexing overhead at write time. It is optimized for semantic similarity queries, so exact-match or structured queries are better served by the direct AgentDB query path.