agent-v3-memory-specialist

Unifies multiple memory backends into AgentDB with HNSW vector indexing for semantic search.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill agent-v3-memory-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-v3-memory-specialist
Source: https://github.com/ruvnet/claude-flow/tree/main/.agents/skills/agent-v3-memory-specialist
Command: npx skills add https://github.com/ruvnet/claude-flow --skill agent-v3-memory-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agentic-flow.

What problem does it solve?

It consolidates seven fragmented memory systems (MemoryManager, DistributedMemorySystem, SwarmMemory, SQLiteBackend, MarkdownBackend, and others) into a single AgentDB-based service, eliminating slow linear searches and inconsistent query interfaces across agent memory stores.

Core Features & Use Cases

  • Unified Memory Service: Implements a UnifiedMemoryService with a single query interface supporting both semantic vector search and structured filtered queries.
  • HNSW Vector Indexing: Adds approximate nearest-neighbor indexing targeting 150x-12,500x search speedups and sub-100ms queries over 1M+ entries.
  • Phased Migration: Provides a three-phase plan to migrate SQLite and Markdown backends into AgentDB while maintaining backward compatibility.
  • Use Case: An agent platform storing coordination patterns across many agents can migrate its SQLite and Markdown memory stores into AgentDB, then run semantic queries like 'agent coordination patterns' with similarity thresholds instead of scanning entries linearly.

Quick Start

Invoke the v3-memory-specialist agent to audit your existing memory backends and generate an AgentDB migration plan with HNSW indexing.

Frequently Asked Questions about agent-v3-memory-specialist

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

FAQPage Schema
How do I unify multiple agent memory backends into one system?

Implement a UnifiedMemoryService that wraps an AgentDB adapter behind a common IMemoryBackend interface, then migrate each legacy backend (SQLite, Markdown, distributed stores) in phases while keeping a backward compatibility layer during transition.

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

HNSW (Hierarchical Navigable Small World) is an approximate nearest-neighbor index that turns O(n) linear memory scans into O(log n) vector searches. This skill targets 150x-12,500x search improvements and sub-100ms queries on datasets over one million entries.

How do I migrate SQLite memory data to AgentDB?

Extract rows from the existing memory_entries table, generate embeddings for each content field, and insert them into AgentDB with the original metadata preserved. The skill provides a phased migration plan covering SQLite and Markdown sources.

Does AgentDB memory support both semantic and structured queries?

Yes. The unified query interface routes semantic queries through the HNSW vector index with similarity thresholds, while structured queries use filters on metadata fields like agent type and timestamp directly against AgentDB.

What are the limitations of HNSW vector search for agent memory?

HNSW provides approximate rather than exact nearest neighbors, so results can miss marginally relevant entries. It also requires embedding generation for every stored entry and tuning parameters like M and efConstruction for the dataset size.