event-communication

Publish and subscribe to Redis pub/sub events for inter-module communication.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/drhayf/GUTTERS --skill event-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-communication
Source: https://github.com/drhayf/GUTTERS/tree/main/.agent/skills/event-communication
Command: npx skills add https://github.com/drhayf/GUTTERS --skill event-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event-communication patterns enable decoupled modules to react to cosmic events and trigger synthesis updates without direct dependencies.

Core Features & Use Cases

  • Redis pub/sub based event bus for publish/subscribe communications between GUTTERS modules.
  • Consistent event naming with scope, entity, action.
  • Integration hooks to trigger Active Memory updates and synthesis processes.
  • Safe, minimal payloads and a no direct module calls policy.

Quick Start

Publish a test event to the global event bus to trigger a synthesis update.

Frequently Asked Questions about event-communication

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

FAQPage Schema
How do I coordinate inter-module events in a decoupled architecture?

You coordinate inter-module events by using a Redis pub/sub event bus to publish and subscribe to messages, allowing modules to communicate without direct dependencies.

What naming conventions should I use for a Redis pub/sub event bus?

A Redis pub/sub event bus should use consistent event naming with scope, entity, and action to ensure predictable message routing across decoupled modules.

How does Redis pub/sub integrate with Active Memory for synthesis updates?

Redis pub/sub integrates with Active Memory through defined hooks that trigger synthesis updates and memory processes automatically when events are published.

Can I trigger module initialization using Redis pub/sub events?

Yes, you can trigger module initialization by subscribing to Redis pub/sub events, allowing modules to react to cosmic events without direct module calls.

What are the payload requirements for inter-module event communication?

Inter-module event communication requires safe, minimal payloads to ensure efficient message passing and maintain a strict no direct module calls policy.

When should I use a Redis pub/sub event bus instead of direct module calls?

Use a Redis pub/sub event bus when decoupled modules need to react to cosmic events or synthesis updates independently, avoiding tight coupling from direct module calls.