Track fleet message delivery with ACK-based retries and failure alerts.
npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-ack
Please help me install this Agent Skill. Skill: fleet-ack Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-ack Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-ack
Fleet messages are not reliably delivered without acknowledgments; this protocol provides an ACK-driven delivery mechanism that tracks, retries on timeout, and raises alerts on failure.
Configure your fleet to enable ACK-based delivery and deploy a node to start sending messages with automatic retries.
High-intent search queries and answers about installing and using this skill.
Fleet message delivery is tracked using ACKs for every message, automatically retrying on timeout. It maintains a persistent retry loop across channels that survives restarts and emits failure alerts after max retries are exceeded.
ACK-based retries are needed because fleet messages are not reliably delivered without acknowledgments. This mechanism tracks delivery, retries on timeout, and raises alerts on failure to ensure critical commands reach all nodes.
Automatic retry timeouts are configured using environment controls for ack_timeout and max_retries. These settings define the wait period and retry threshold before the system emits failure alerts for unreached fleet messages.
Yes, the fleet ACK retry state survives restarts by using SQLite for persistent storage. This persistent retry loop retains pending message acknowledgments and retry counts across outages and application restarts.
When fleet messages exceed the maximum retry limit, the system emits failure alerts to surface unreached messages within sessions. This surfaces persistent delivery failures for manual intervention.
Yes, a SQLite database is required because the system uses FleetNerveStore for persistent ACK tracking. SQLite stores delivery state and retry counters, enabling the retry loop to survive restarts and outages.
shreed27Store and retrieve encrypted API credentials for trading platforms.
mdmagnuson-creatorLog automated test failures to verification-failures.json and test-debt.json.
masermediagroup-stackCoordinate asynchronous microservice communication using message queues and brokers.
williamzujkowskiDesign message queue patterns with DLQs, idempotency, and ordering across Kafka, RabbitMQ, SQS, Azure Service Bus, and Pub/Sub.
