skills.rest
supportersimulator
supportersimulatorCOMMUNITY
Explore all skills by this author →
GitHub

fleet-send

Route fleet messages through a 7-priority cascade with delivery confirmation.

2|Updated Apr 5, 2026
Search Tags:#automation#messaging#multi-channel#http#self-healing#nats#fleet
One-click install
npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-send
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fleet-send
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-send
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-send

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fleet messaging across nodes with a deterministic, multi-channel delivery that remains reliable in hostile networks.

Core Features & Use Cases

  • Multi-channel delivery using a 7-priority cascade with a final direct-text channel, each with per-channel timeouts.
  • Supports message types including context, task, reply, alert, broadcast, and sync for fleet coordination.
  • Built-in self-healing: automatic repair of broken channels and optional integration with fleet repair workflows.

Quick Start

Send a test message to a target node using the provided curl example or the fleet-send CLI script to verify end-to-end delivery.

Frequently Asked Questions about fleet-send

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

FAQPage Schema
How do I send messages reliably across multiple nodes in a hostile network?▼

Cross-node messaging in a fleet uses a 7-priority cascade with a final direct-text channel to guarantee delivery. Each channel has per-channel timeouts and delivery confirmation to maintain reliability even in hostile networks.

How does self-healing messaging handle broken channels during fleet broadcasts?▼

Self-healing messaging automatically repairs broken channels during fleet broadcasts and optionally integrates with fleet repair workflows. This ensures multi-channel delivery paths are restored without manual intervention.

Can I use HTTP and NATS for multi-channel message delivery across my fleet?▼

Yes, you can use HTTP and NATS for multi-channel message delivery across your fleet. The system routes context, tasks, alerts, and broadcasts through an ordered 7-priority cascade using these protocols to ensure reliable delivery.

What is the best way to automate cross-node alert delivery when network connections fail?▼

The best way to automate cross-node alert delivery when connections fail is using an ordered multi-channel cascade with self-healing. It automatically repairs broken channels and applies per-channel timeouts to guarantee message delivery.

What message types are supported for fleet coordination and task routing?▼

Supported message types for fleet coordination and task routing include context, task, reply, alert, broadcast, and sync. These are delivered across machines through a 7-priority cascade to ensure reliable communication.

Related Skills

Explore More Software Engineering Skills→
supportersimulatorsupportersimulator
2

fleet-protocol

Enforce multi-channel self-healing messaging across fleet nodes with prioritized timeouts.

Community
Advanced
supportersimulatorsupportersimulator
2

fleet-watchdog

Monitor fleet health and escalate automatic repairs across nodes.

Community
Advanced
supportersimulatorsupportersimulator
2

fleet-repair

Coordinate L1-L4 repair escalation for degraded fleet channels via SSH.

Community
Advanced
eprouvezeeprouveze

relay

Parse Gmail drafts with [LEX-RELAY] subjects and triage by priority.

Community
Advanced