triad-sync-protocol

Name: triad-sync-protocol
Availability: InStock
Author: Heretek-AI

Synchronize agent state and health via HTTP endpoints within an OpenClaw gateway.

Updated Mar 24, 2026

Search Tags:#consensus #coordination #http #health-check #gateway #inter-agent #state-sync

Ready to run

npx skills add https://github.com/Heretek-AI/heretek-skills --skill triad-sync-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triad-sync-protocol
Source: https://github.com/Heretek-AI/heretek-skills/tree/main/skills/triad-sync-protocol
Command: npx skills add https://github.com/Heretek-AI/heretek-skills --skill triad-sync-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sqlite3, and includes scripts (resource) components.

What problem does it solve?

Direct HTTP-based inter-agent communication enables a single gateway to coordinate state, health, and consensus without multi-node orchestration.

Core Features & Use Cases

Direct HTTP endpoints (/state, /health, /broadcast, /sync) for synchronized state across agents.
Lightweight consensus plumbing and health checks within a single OpenClaw instance.
Use cases include intra-gateway triad coordination, state reconciliation, and rapid health verification among steward, triads, examiner, explorer, sentinel, and coder.

Quick Start

Start the internal HTTP sync server and query the /state endpoint to verify initial state.

Frequently Asked Questions about triad-sync-protocol

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

FAQPage Schema

How do I synchronize state and health across multiple agents in a single gateway?▼

State synchronization and health monitoring across agents in a single gateway use direct HTTP endpoints like /state and /sync. This allows rapid state replication and health verification without requiring multi-node orchestration.

Can I broadcast consensus votes locally without setting up a distributed network?▼

Consensus broadcasting can be handled locally through an HTTP /broadcast endpoint backed by a local ledger. This logs votes and coordinates consensus plumbing within a single OpenClaw gateway instance.

Do I need Node.js and sqlite3 to run HTTP-based inter-agent coordination?▼

Node.js and sqlite3 are required dependencies for this HTTP-based inter-agent coordination. They provide the runtime environment and local ledger storage needed to log votes and manage state synchronization.

How do I configure HTTP endpoints for triad coordination and health checks?▼

Configuring triad coordination involves setting a configurable SYNC_PORT and node id. You then query endpoints like /state and /health to verify initial state and monitor agent status across Steward, Alpha, Beta, and Charlie.

What's the best way to monitor agent health within a single OpenClaw instance?▼

Monitoring agent health within a single OpenClaw instance is done via the /health HTTP endpoint. It provides rapid health verification for agents like Examiner, Explorer, Sentinel, and Coder without multi-node overhead.

When should I avoid using direct HTTP synchronization for inter-agent communication?▼

Direct HTTP synchronization is designed for a single gateway deployment. You should avoid this approach if your architecture requires multi-node orchestration or distributed network communication across separate instances.