fleet-chain

Coordinate multi-node task chains with strict step sequencing via HTTP endpoints.

2|Updated Apr 5, 2026

Search Tags:#automation #workflow #orchestration #fleet #http-api #multinode

Ready to run

npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-chain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fleet-chain
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-chain
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chains are ordered sequences of tasks dispatched across fleet nodes. Each step runs only after the previous step succeeds. If any step fails, the chain halts.

Core Features & Use Cases

End-to-end chain execution across nodes with automatic sequencing and halt on failure
Remote step completion signaling and chain status queries
HTTP endpoints for starting chains, listing chains, and retrieving chain status
Per-step timeouts and a multi-channel dispatch mechanism to ensure delivery reliability

Quick Start

Start a chain by POSTing a JSON payload with an ordered steps array to the /chain endpoint and monitor its progress via the /chain/<id> status endpoint.

Frequently Asked Questions about fleet-chain

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

FAQPage Schema

How do I automate multi-node build-test-deploy pipelines with strict step sequencing?▼

Multi-node build-test-deploy pipelines require strict step sequencing, which you achieve by dispatching ordered task chains across fleet nodes. Each step advances only after the previous step succeeds, ensuring deterministic cascade execution and predictable progress across the fleet.

How do I start a multi-step task chain and query its execution status?▼

To start a multi-step task chain, POST a JSON payload containing an ordered steps array to the /chain HTTP endpoint. You can then monitor execution by querying the /chain/<id> status endpoint to retrieve current chain progress and state.

What happens when a step fails during multi-node workflow orchestration?▼

When a step fails during multi-node workflow orchestration, the chain halts immediately to prevent downstream execution. This halt-on-failure mechanism ensures recoverability and isolates failures within the deterministic cascade without corrupting subsequent steps.

How do per-step timeouts work in fleet-wide task orchestration?▼

Per-step timeouts in fleet-wide task orchestration enforce maximum execution durations for individual steps. Combined with remote completion signaling and a multi-channel dispatch mechanism, these timeouts ensure reliable delivery and prevent stalled steps from blocking the chain cascade.

Can I use HTTP endpoints to list active chains across fleet nodes?▼

Yes, you can use HTTP endpoints to list active chains across fleet nodes. The orchestration system exposes HTTP endpoints for starting chains, listing existing chains, and retrieving detailed chain status, making fleet-wide task coordination accessible via API requests.