skills.rest
TeoSlayer
TeoSlayerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pilot-fleet-health-monitor-setup

Orchestrate fleet health monitoring across three agents with webhook alert routing.

7|3|Updated Apr 8, 2026
Search Tags:#metrics#alerting#webhooks#fleet#health-monitoring#pilot-health#pilot-alert
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-fleet-health-monitor-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pilot-fleet-health-monitor-setup
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-fleet-health-monitor-setup
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-fleet-health-monitor-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy and manage a fleet-wide health monitoring system across multiple agents to continuously detect service health issues, correlate metrics, and route alerts to human operators.

Core Features & Use Cases

  • Deploy three coordinated roles (web-monitor, db-monitor, alert-hub) with built-in health checks, alerting, and metrics collection.
  • Centralize alerts by aggregating, deduplicating, and forwarding critical events to external channels (Slack, PagerDuty) via webhooks.
  • Facilitate secure onboarding with handshakes and well-defined data flows between monitors and the hub.

Quick Start

Install the required skills for each role with clawhub, set unique hostnames, and perform the necessary handshakes to connect the fleet.

Frequently Asked Questions about pilot-fleet-health-monitor-setup

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

FAQPage Schema
How do I set up fleet health monitoring across multiple agents?▼

Centralized alerting works by aggregating and deduplicating critical events from monitors, then forwarding them to external channels like Slack or PagerDuty via webhooks. The alert-hub role handles this centralized notification delivery.

What do I need to deploy unified health checks for my services?▼

Deploying unified health checks requires defining three agent roles, establishing mutual handshakes for secure onboarding, and configuring data flows. You must also define ports, specifically port 1002 with the health-alert topic, to enable end-to-end monitoring.

Can I use this fleet monitoring setup for metric aggregation and webhook notifications?▼

Yes, this setup applies to deployments requiring unified health checks, metric aggregation, and centralized notification delivery via webhooks. It continuously detects service health issues and correlates metrics across the configured agents.

Why do my fleet health monitors require mutual handshakes and defined ports?▼

Mutual handshakes and defined ports, like port 1002, are required to facilitate secure onboarding and establish well-defined data flows between the monitors and the alert-hub. This ensures reliable end-to-end monitoring and alert routing.

Related Skills

Explore More Software Engineering Skills→
TeoSlayerTeoSlayer
7

pilot-brand-protection-setup

Deploy a four-agent brand protection system with scanner, classifier, enforcer, and dashboard roles.

Community
Advanced
ankraioankraio
26

ankra-alerts-webhooks

Route cluster alerts to external systems via webhooks with AI incident context.

Official
Intermediate
atholaathola
326

service-registry

Manage external service connections, configurations, and health checks across multiple services.

Community
Intermediate
giuseppe-trisciuogliogiuseppe-trisciuoglio
322

spring-boot-actuator

Configure Spring Boot Actuator endpoints, health probes, and Micrometer metrics.

Community
Intermediate