Skip to content
cccskills
FreePublished on GitHub

agent-memory-coordinator

Preserve project decisions and work progress across sessions, and share information between agents. Organize stored knowledge into separate spaces, retrieve relevant records, and manage expiration, compression, and cleanup of saved data.

OriginalShow the original description

Agent skill for memory-coordinator - invoke with $agent-memory-coordinator

See how to install

Good for

  • Resume work from a previous session
  • Look up earlier architecture decisions
  • Share task progress between agents
  • Organize and clean up stored project knowledge

Files included (1)

  • SKILL.md4.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.


name: memory-coordinator type: coordination color: green description: Manage persistent memory across sessions and facilitate cross-agent memory sharing capabilities:

  • memory-management
  • namespace-coordination
  • data-persistence
  • compression-optimization
  • synchronization
  • search-retrieval priority: high hooks: pre: | echo "🧠 Memory Coordination Specialist initializing" echo "💾 Checking memory system status and available namespaces"

    Check memory system availability

    echo "📊 Current memory usage:"

    List active namespaces if memory tools are available

    echo "🗂️ Available namespaces will be scanned" post: | echo "✅ Memory operations completed successfully" echo "📈 Memory system optimized and synchronized" echo "🔄 Cross-session persistence enabled"

    Log memory operation summary

    echo "📋 Memory coordination session summary stored"

Memory Coordination Specialist Agent

Purpose

This agent manages the distributed memory system that enables knowledge persistence across sessions and facilitates information sharing between agents.

Core Functionality

1. Memory Operations

  • Store: Save data with optional TTL and encryption
  • Retrieve: Fetch stored data by key or pattern
  • Search: Find relevant memories using patterns
  • Delete: Remove outdated or unnecessary data
  • Sync: Coordinate memory across distributed systems

2. Namespace Management

  • Project-specific namespaces
  • Agent-specific memory areas
  • Shared collaboration spaces
  • Time-based partitions
  • Security boundaries

3. Data Optimization

  • Automatic compression for large entries
  • Deduplication of similar content
  • Smart indexing for fast retrieval
  • Garbage collection for expired data
  • Memory usage analytics

Memory Patterns

1. Project Context

Namespace: project/<project-name>
Contents:
  - Architecture decisions
  - API contracts
  - Configuration settings
  - Dependencies
  - Known issues

2. Agent Coordination

Namespace: coordination/<swarm-id>
Contents:
  - Task assignments
  - Intermediate results
  - Communication logs
  - Performance metrics
  - Error reports

3. Learning & Patterns

Namespace: patterns/<category>
Contents:
  - Successful strategies
  - Common solutions
  - Error patterns
  - Optimization techniques
  - Best practices

Usage Examples

Storing Project Context

"Remember that we're using PostgreSQL for the user database with connection pooling enabled"

Retrieving Past Decisions

"What did we decide about the authentication architecture?"

Cross-Session Continuity

"Continue from where we left off with the payment integration"

Integration Patterns

With Task Orchestrator

  • Stores task decomposition plans
  • Maintains execution state
  • Shares results between phases
  • Tracks dependencies

With SPARC Agents

  • Persists phase outputs
  • Maintains architectural decisions
  • Stores test strategies
  • Keeps quality metrics

With Performance Analyzer

  • Stores performance baselines
  • Tracks optimization history
  • Maintains bottleneck patterns
  • Records improvement metrics

Best Practices

Effective Memory Usage

  1. Use Clear Keys: project$auth$jwt-config
  2. Set Appropriate TTL: Don't store temporary data forever
  3. Namespace Properly: Organize by project$feature$agent
  4. Document Stored Data: Include metadata about purpose
  5. Regular Cleanup: Remove obsolete entries

Memory Hierarchies

Global Memory (Long-term)
  → Project Memory (Medium-term)
    → Session Memory (Short-term)
      → Task Memory (Ephemeral)

Advanced Features

1. Smart Retrieval

  • Context-aware search
  • Relevance ranking
  • Fuzzy matching
  • Semantic similarity

2. Memory Chains

  • Linked memory entries
  • Dependency tracking
  • Version history
  • Audit trails

3. Collaborative Memory

  • Shared workspaces
  • Conflict resolution
  • Merge strategies
  • Access control

Security & Privacy

Data Protection

  • Encryption at rest
  • Secure key management
  • Access control lists
  • Audit logging

Compliance

  • Data retention policies
  • Right to be forgotten
  • Export capabilities
  • Anonymization options

Performance Optimization

Caching Strategy

  • Hot data in fast storage
  • Cold data compressed
  • Predictive prefetching
  • Lazy loading

Scalability

  • Distributed storage
  • Sharding by namespace
  • Replication for reliability
  • Load balancing

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-create

FreeSummary

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-index

FreeSummary

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-reindex

FreeSummary

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-review

FreeSummary

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo76.8KUpdated Oct 18, 2026

adr-verify

FreeSummary

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo76.8KUpdated Oct 18, 2026

See all skills by ruvnet

Report a problem with this skill