fleet-repair

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repair escalation for degraded fleet channels to maintain end-to-end connectivity between peers, ensuring messages continue to flow as the fleet heals.

Core Features & Use Cases

  • Automatic L1-L4 escalation when P1/P2 channels fail, enabling self-healing repair flows.
  • SSH-based repair orchestration with optional human approval for remote actions.
  • Fleet-wide repair agents that diagnose and fix broken channels across multiple nodes.
  • Real-world scenario: when NATS and HTTP links are degraded, the system guides recovery without data loss and with auditable logs.

Quick Start

Configure your fleet in .multifleet/config.json and allow automatic escalation to initiate repairs when primary channels fail.

Frequently Asked Questions about fleet-repair

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

FAQPage Schema
How do I automate fleet repair escalation for degraded NATS and HTTP channels?

Fleet repair escalation automates recovery for degraded NATS and HTTP channels by triggering L1-L4 self-healing repair flows across multi-node peers to restore primary connectivity. It requires a .multifleet/config.json setup and SSH access to target nodes to orchestrate remote actions.

What are the prerequisites for setting up SSH-based remote repair orchestration?

SSH-based remote repair orchestration requires SSH access to target nodes, a configured .multifleet/config.json file, and integration with existing fleet tooling to trigger, monitor, and log repairs across the multi-node peer network.

Does the fleet repair escalation process require human approval for remote actions?

Fleet repair escalation supports optional human approval for remote SSH-based repair actions, allowing teams to enforce manual oversight on critical recovery steps while maintaining automated self-healing for standard L1-L4 channel failures.

How does self-healing repair work when P1 and P2 fleet channels fail?

Self-healing repair activates automatic L1-L4 escalation when P1 and P2 channels fail, diagnosing and fixing broken links across multiple nodes to ensure messages continue flowing without data loss and generating auditable repair logs.

Can I use fleet repair agents to fix broken connectivity across multiple nodes simultaneously?

Fleet-wide repair agents diagnose and fix broken channels across multiple nodes simultaneously, coordinating end-to-end repair escalation to restore primary connectivity between peers while maintaining auditable logs of all remote operations.