pilot-status-page-setup

To set up an automated status page pipeline, this Skill deploys a three-agent architecture using pilotctl to monitor service health, aggregate status, and publish incidents to subscribers across multiple hosts.

A three-agent status page setup coordinates a monitor, aggregator, and publisher agent to collect health checks, compute overall status, and broadcast incidents using the Pilot Protocol for trust handshakes and data-flow wiring.

You configure incident management for multiple hosts by installing pilot-health, pilot-event-filter, and pilot-webhook-bridge skills on the three agents, setting hostnames, and establishing required trust handshakes.

Yes, the Pilot Protocol supports trust handshakes for automated incident communication by defining role manifests and orchestrating peer data flows between the monitor, aggregator, and publisher agents.

Yes, you can use clawhub and pilotctl to broadcast service incidents by deploying the publisher agent, which computes overall status from the aggregator and pushes incident updates to subscribers.

The status page pipeline requires explicitly configuring three distinct agents and establishing peer trust handshakes between them, meaning single-node deployments or untrusted host environments cannot support this orchestration.