federated-memory

Implement federated long-term memory with semantic retrieval and read-only MCP search tools.

8|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drewid74/ai_skills --skill federated-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: federated-memory
Source: https://github.com/drewid74/ai_skills/tree/main/federated-memory
Command: npx skills add https://github.com/drewid74/ai_skills --skill federated-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Federated-memory helps an AI agent retain and recall important information across sessions by storing knowledge in a searchable memory system and enabling read-only sharing across multiple agents without unsafe write sharing.

Core Features & Use Cases

  • Query-layer memory federation: lets multiple agents access each other’s stored knowledge via read-only MCP tools while preventing conflicting cross-writes.
  • Tiered memory architecture: routes information to working memory, semantic recall over past conversations, and permanent archival knowledge/decisions.
  • Vector + optional graph retrieval: uses Qdrant or pgvector for semantic search and adds a graph layer (FalkorDB/Neo4j) when multi-hop relationship queries are required.
  • Operational guardrails: includes embedding selection and migration strategy, dedup via content hashing, and retention policies to stop memory from growing unbounded.
  • Use Case: When an agent can’t remember prior decisions about “deployment rollback policy,” use semantic search to retrieve those decisions and ensure a consistent answer across future sessions and agent teams.

Quick Start

Ask your AI to design a federated memory setup that uses pgvector for archival recall, deduplicates entries with content hashes, and exposes MCP tools for read-only cross-agent memory search.

Frequently Asked Questions about federated-memory

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

FAQPage Schema
How do I share long-term agent memory safely across multiple sessions?

Share long-term agent memory across sessions by implementing a federated memory architecture that uses read-only MCP tools for cross-agent retrieval, enforcing deduplication and retention policies to prevent conflicting writes.

What is the best way to perform semantic retrieval for past AI conversations using pgvector or Qdrant?

Perform semantic retrieval for past conversations by routing memory through a tiered architecture that uses pgvector or Qdrant for fast similarity search, optionally adding a graph layer like Neo4j for multi-hop relationship queries.

How do I stop unbounded memory growth and deduplicate agent knowledge bases?

Stop unbounded memory growth by applying retention policies and deduplicating stored knowledge bases using content hashing, ensuring only unique information is persisted during multi-agent sessions.

Can I use read-only MCP tools to let multiple AI agents query the same memory without write conflicts?

Yes, you can expose read-only MCP search tools to let multiple agents query the same federated memory, strictly prohibiting cross-agent write paths to avoid data conflicts and ensure safe knowledge retrieval.

Does federated memory support multi-hop relationship queries across different agent domains?

Federated memory supports multi-hop relationship queries across agent domains by integrating an optional graph layer using FalkorDB or Neo4j alongside the primary vector store for complex semantic retrieval.

When do I need a tiered memory architecture for my multi-agent AI system?

You need a tiered memory architecture when your multi-agent system must route information dynamically between working memory, semantic recall, and permanent archival knowledge to persist past decisions effectively.