Fleet Control

Check Aeon instance health and compute next actions via gh api.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill fleet-control-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Fleet Control
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/fleet-control
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill fleet-control-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor and manage multiple Aeon instances by orchestrating health checks, status aggregation, and automated skill dispatch to keep fleets healthy with minimal manual intervention.

Core Features & Use Cases

  • Health checks across the fleet: verify per-instance health, reachability, and status.
  • Dispatch mode: trigger skills on selected healthy/warning/degraded instances.
  • Status snapshots and logs: produce actionable insights for operators, including per-instance actions.

Quick Start

Check health of all managed Aeon instances and generate an actionable per-instance plan.

Frequently Asked Questions about Fleet Control

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

FAQPage Schema
How do I automate health checks across multiple Aeon instances?

Automate fleet health checks by running parallel reachability tests and metadata collection on all registered Aeon instances. The process categorizes each instance as healthy, degraded, or unreachable and computes a recommended next action.

How does fleet monitoring handle stale or pending instances?

Fleet monitoring identifies stale, pending, or archived instances by computing deltas against prior state using local memory files. It categorizes instance health status and logs outcomes to update fleet state records.

Can I trigger skill dispatch on specific instances after a health check?

Yes, you can trigger skill dispatch on selected healthy, warning, or degraded instances after health checks complete. Dispatch mode automates targeted actions based on the computed fleet status.

Do I need GitHub API calls to monitor Aeon fleet reachability?

Yes, monitoring Aeon fleet reachability requires using gh api calls and local memory files. The orchestration process collects per-instance metadata and updates state logs to track fleet health.

What is the best way to orchestrate workflow monitoring for a fleet of instances?

The best way to orchestrate workflow monitoring is applying parallel health checks to all registered instances, categorizing status, and generating actionable per-instance plans with automated notifications.

Why are my fleet health checks showing instances as unreachable?

Fleet health checks mark instances as unreachable when parallel reachability tests fail to collect per-instance metadata. The system logs these outcomes and computes a recommended next action to resolve the issue.