agent-memory-coordinator

Store, retrieve, search, and sync memories across namespaces with TTL and encryption.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/Ethansuttor/QUANTIFIED --skill agent-memory-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-memory-coordinator
Source: https://github.com/Ethansuttor/QUANTIFIED/tree/main/.gemini/skills/ruflo/.agents/skills/agent-memory-coordinator
Command: npx skills add https://github.com/Ethansuttor/QUANTIFIED --skill agent-memory-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory coordination and persistence across sessions and agents to enable seamless knowledge continuity and cross-agent collaboration.

Core Features & Use Cases

  • Memory Operations: Store, retrieve, search, delete, and synchronize memories across namespaces with optional TTL and encryption.
  • Namespace & Coordination: Manage project-, agent-, and shared-space memory boundaries to prevent leakage and enable scoped access.
  • Cross-Session Persistence & Retrieval: Maintain decision traces and patterns across sessions, supporting fast lookup and auditability.
  • Use Case: Imagine a product launch where decisions, experiments, and results are stored once and retrieved by any agent in future sessions.

Quick Start

Store a memory entry describing a critical API design decision under namespace coordination/project-alpha to enable cross-session retrieval.

Frequently Asked Questions about agent-memory-coordinator

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

FAQPage Schema
How do I persist memory across sessions for multiple agents?

Namespace boundaries manage project, agent, and shared-space memory scopes to prevent data leakage and enable scoped access. This coordination ensures agents only access memory within their designated project or shared boundaries.

Can I set a TTL and encryption for stored memory entries?

Yes, memory operations support optional Time-To-Live (TTL) and encryption when storing entries. This ensures sensitive data is automatically expired and secured while maintaining efficient retrieval and auditability across sessions.

What is the best way to retrieve past decisions in a multi-agent workflow?

The best way to retrieve past decisions is to store critical entries once under a specific namespace, like a project identifier. Any agent can then search and retrieve these memories in future sessions with fast lookup and audit log support.

Does this memory coordination approach support audit logs and compression?

Yes, the memory management process provides audit logs for tracking retrieval and storage actions. It also enables efficient compression, ensuring scalable memory coordination across large multi-agent workflows without losing historical patterns.