agentleFS
fidgetcodingfidgetcoding/fidgetflo/.agents/skills/agent-memory-coordinator/SKILL.md

agent-memory-coordinator

Skill1 starsChanged 7 months agoMITView on GitHub

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

5 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Delete: Remove outdated or unnecessary data

    line 46
  2. Distinctive:

    Set Appropriate TTL: Don't store temporary data forever

    line 133
  3. Distinctive:

    Regular Cleanup: Remove obsolete entries

    line 136

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.