memory-blackboard

Implement a shared memory blackboard protocol for multi-agent session communication.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ryasrk/AgentBrokeTheMatrix-CopilotVersion --skill memory-blackboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-blackboard
Source: https://github.com/ryasrk/AgentBrokeTheMatrix-CopilotVersion/tree/main/.github/skills/memory-blackboard
Command: npx skills add https://github.com/ryasrk/AgentBrokeTheMatrix-CopilotVersion --skill memory-blackboard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the inefficiency and redundancy in multi-agent workflows by establishing a shared memory protocol, preventing duplicate work and enabling seamless context sharing between agents.

Core Features & Use Cases

  • Session Memory as Blackboard: Utilizes a structured directory (/memories/session/) for inter-agent communication, result caching, and progressive context building.
  • Reduces Token Waste: Prevents multiple agents from re-exploring the same codebase or re-deriving the same information, leading to significant token savings.
  • Enables Cross-Agent Context: Facilitates complex, multi-phase tasks where later stages depend on the outcomes of earlier ones, and supports cross-domain collaboration.
  • Use Case: In a multi-phase project (e.g., AI → Backend → Frontend), the AI phase writes its decisions to ai-phase-results.md. The Backend phase then reads this file to ensure its implementation aligns with AI requirements, avoiding rework.

Quick Start

Instruct the planner to write the initial project context to the session memory blackboard.

Frequently Asked Questions about memory-blackboard

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

FAQPage Schema
How do I share memory and context between multiple AI agents in a workflow?

To share context between multiple AI agents, you can implement a blackboard pattern within session memory. This creates a structured directory for inter-agent communication, enabling agents to read previous outcomes and build progressive context without redundant exploration.

Why does my multi-agent workflow waste tokens re-exploring the same codebase?

Multi-agent workflows waste tokens when agents lack shared memory and independently re-derive the same information. Implementing a blackboard pattern caches results in session memory, preventing duplicate exploration and significantly reducing token usage across the workflow.

How do I implement a blackboard pattern for cross-domain multi-agent tasks?

Implementing a blackboard pattern for cross-domain tasks involves writing phase results to a shared session memory directory. Later phases read these cached files to align their execution with earlier requirements, enabling seamless progressive context building across different domains.

Can I use session memory to cache results for multi-phase project workflows?

Yes, you can use session memory to cache results for multi-phase workflows. By writing decisions to structured files within a session directory, subsequent phases retrieve the cached context directly, ensuring later implementations align with earlier project outcomes.

What is the best way to prevent duplicate work in multi-agent systems?

The best way to prevent duplicate work in multi-agent systems is adopting a shared memory protocol using the blackboard pattern. This approach facilitates efficient context sharing by caching derived information, ensuring agents do not re-explore identical domains or re-derive existing data.