fleet-healer

Automate fleet health diagnostics and restore degraded NATS, HTTP, SSH, and seed channels.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-healer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fleet-healer
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-healer
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-healer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fleet health and reliability across a distributed fleet are fragile; this skill automatically spawns background healing agents to diagnose degraded communication channels and restore them to an ideal state, reducing manual intervention and downtime.

Core Features & Use Cases

  • Automated health checks and autonomous restoration of degraded channels across the fleet.
  • Background healing agents diagnose and repair NATS, HTTP, SSH, and seed-based pathways, converging all peers to ideal state.
  • Use Case: In a disrupted fleet due to network changes, the healer re-establishes full connectivity without user action.

Quick Start

Start the fleet-healer to automatically diagnose and restore all fleet channels to ideal state.

Frequently Asked Questions about fleet-healer

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

FAQPage Schema
How do I automatically restore degraded SSH and NATS communication channels across a distributed fleet?▼

Automated fleet healing restores degraded SSH and NATS channels by spawning background agents that diagnose connectivity, repair peer-to-peer pathways, and verify all peers converge to an ideal state without manual intervention.

What is automated fleet healing for distributed communication reliability?▼

Fleet healing is an automated background process that diagnoses degraded communication channels across distributed peers and restores them to full reliability, minimizing manual troubleshooting and downtime during network disruptions.

Do I need SSH keys in ~/.ssh/ to run automated fleet channel diagnostics and repairs?▼

Yes, automated fleet channel diagnostics require SSH keys located in the ~/.ssh/ directory to authorize background agents to connect, diagnose, and repair SSH pathways across the distributed peers.

How does background fleet healing handle network disruptions and repair HTTP tunnels?▼

Background fleet healing handles network disruptions by spawning autonomous agents that diagnose and repair HTTP tunnels, NATS peer-to-peer connections, and seed-based recovery pathways, escalating issues when automatic restoration fails.

What's the best way to converge all distributed peers to an ideal communication state after network changes?▼

The best way to converge distributed peers to an ideal communication state is using automated background healing agents that diagnose, repair, and verify health across NATS, HTTP, SSH, and seed-based pathways with escalation support.

Where are fleet health diagnostic results logged during automated channel restoration?▼

Fleet health diagnostic results are logged to the /tmp/atlas-agent-results directory, capturing background agent tasks that diagnose, repair, and verify communication channel health during the automated restoration process.