redis-coordinator

Orchestrate container-based CFN Loop execution with Redis-backed state management.

14|2|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/masharratt/claude-flow-novice --skill redis-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: redis-coordinator
Source: https://github.com/masharratt/claude-flow-novice/tree/main/.claude/cfn-loop-orchestration-v2/lib/orchestrator/src/redis/redis-coordinator.ts
Command: npx skills add https://github.com/masharratt/claude-flow-novice --skill redis-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a Redis-based coordination core for CFN Loop tasks, including task context, agent state, and consensus data.

Core Features & Use Cases

  • Redis integration: Init, context, registration, and consensus collection.
  • Robust error handling: Typed errors for coordination failures.
  • Security: Input validation, constraints for task/agent IDs.

Quick Start

Create a RedisCoordinator with proper config and start coordinating task flows.

Frequently Asked Questions about redis-coordinator

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

FAQPage Schema
How do I coordinate multiple agents and collect consensus with Redis?

Redis-backed coordination orchestrates parallel and sequential agent execution, manages task state and progress monitoring, and collects consensus decisions across agents. The Skill provides a command-line interface to initialize Redis contexts, spawn agents, track their completion, and aggregate results into a shared consensus layer.

Can I use Redis coordination for long-running container-based workflows?

Yes. Redis coordination supports long-running CFN workflows by maintaining persistent task context, agent registration, and consensus data in Redis. It handles task authentication, progress monitoring, and failure tolerance across docker-based agents, enabling reliable orchestration of extended asynchronous processes.

What error handling does Redis-backed coordination provide?

The Skill includes typed errors for coordination failures, input validation for task and agent IDs, and constraint enforcement. These mechanisms catch failures during agent spawning, state synchronization, and consensus collection, enabling you to diagnose and recover from coordination breakdowns.

How do I configure Redis coordination for different deployment scales?

Redis coordination supports three mode configurations—MVP, Standard, and Enterprise—each tuned for different scale and complexity requirements. You select the mode via command-line parameters when initializing the coordinator, adjusting parallelism, gate checks, and failure tolerance accordingly.

When should I use Redis for agent state management instead of other backends?

Redis coordination excels when you need fast, in-memory state persistence for real-time agent tracking, consensus collection, and gate checks across distributed tasks. It suits scenarios requiring low-latency reads of shared agent status and rapid consensus updates, particularly in CFN Loop implementations.

What are the entry requirements before starting agent coordination?

You need a running Redis instance, docker-based agents ready to spawn, and defined CFN Loop task workflows. The Skill handles initialization and context setup; you provide task definitions, agent images, and consensus rules via the command-line orchestration interface.