fleet-status

Aggregates per-node status, sessions, and tasks into a live fleet view.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Fleet-status provides immediate visibility into fleet health by aggregating per-node status, active sessions, running tasks, and connectivity health.

Core Features & Use Cases

  • Live fleet view by merging local daemon data with cached heartbeats
  • Fallback HTTP probe for stale UDP heartbeats to ensure resilience
  • Useful for debugging connectivity, wake/repair workflows, and workload assignment

Quick Start

Run the fleet-status skill to fetch the current live fleet view from your local daemon.

Frequently Asked Questions about fleet-status

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

FAQPage Schema
How do I monitor fleet health and aggregate per-node status across multiple machines?

Monitor fleet health by aggregating per-node status, active sessions, and running tasks into a unified live view. It merges local daemon data with cached UDP heartbeats to provide instant visibility across multiple machines.

What happens when UDP heartbeats become stale during fleet monitoring?

When UDP heartbeats become stale, fleet monitoring automatically triggers an HTTP fallback probe. This ensures resilient connectivity checks and validates node freshness even if primary heartbeat packets are dropped.

Can I use fleet status for debugging connectivity and wake/repair workflows?

Yes, you can use fleet status for debugging connectivity and managing wake/repair workflows. It provides deterministic data collection and validates health signals to quickly identify unresponsive nodes.

How do I get a live fleet view from my local daemon?

Get a live fleet view by running the fleet-status skill to fetch current data from your local daemon. It instantly merges local daemon records with cached heartbeats to display real-time node status.

Do I need any external dependencies to track node sessions and tasks?

No external dependencies are required to track node sessions and tasks. The skill operates independently using scripts to collect deterministic data from UDP heartbeats and HTTP fallbacks.