Pilot Status Page Setup

Deploy a status page pipeline with 3 agents that automate service monitoring, status aggregation, and public incident communication. Use this skill when: 1....

Security Scan

The skill's instructions and requirements are coherent with its stated purpose (setting up a 3‑agent status page pipeline); the only mismatches are a minor metadata omission about a config path and the normal risk that it installs other pilot-* skills via clawhub which you should trust before running.

Purpose & Capability

Name/description (deploying monitor/aggregator/publisher agents for a status page) match the runtime actions: installing role-specific pilot-* skills with clawhub, setting hostnames and performing handshakes with pilotctl, and writing a role manifest. Required binaries (pilotctl, clawhub) are appropriate for these steps.

Instruction Scope

The instructions stay within the stated purpose (install skills, set hostname, create role manifest, perform handshakes, and subscribe/publish events). One scope mismatch: the metadata lists no required config paths, yet the instructions explicitly write a manifest to ~/.pilot/setups (creates files under the user's home). This is a documentation/metadata omission rather than unexplained behavior.

Install Mechanism

This is an instruction-only skill with no install spec or bundled code. Risk from installation comes from running the external clawhub install commands at runtime (which will fetch and install other pilot-* skills). The skill itself does not download or execute third-party code directly.

Credentials

The skill requests no environment variables or credentials and does not try to access unrelated secrets. It does instruct creating files under ~/.pilot, which is appropriate for a per-user agent setup and consistent with the described functionality.

Persistence & Privilege

always is false and the skill is user-invocable — normal for this type of setup helper. The skill writes its own manifest under ~/.pilot/setups (expected for setting up an agent) and does not request system-wide privileges or modify other skills' configurations in the instructions.

Assessment

This skill appears to do what it says: install pilot-* capabilities, set hostnames, write a per-user manifest (~/.pilot/setups), and perform agent handshakes. Before running it: 1) ensure pilotctl and clawhub are legitimate/trusted binaries on the host; 2) review what the clawhub install commands will fetch (the pilot-* skills) because those will be downloaded/installed by clawhub; 3) be comfortable creating files under ~/.pilot/setups (the SKILL.md writes there but the metadata omitted that config path); and 4) confirm the source/homepage (https://pilotprotocol.network) and the individual pilot-* skills if you need higher assurance. If you need help auditing what clawhub will install (or verifying pilotctl), collect the clawhub install output or the upstream package sources and I can review them.

Status Page Setup

Deploy 3 agents that automate service monitoring, status aggregation, and incident communication.

Roles

Role	Hostname	Skills	Purpose
monitor	<prefix>-monitor	pilot-health, pilot-cron, pilot-metrics	Pings endpoints, checks response times, detects outages
aggregator	<prefix>-aggregator	pilot-event-filter, pilot-dataset, pilot-audit-log	Combines health checks into system status, tracks uptime
publisher	<prefix>-publisher	pilot-webhook-bridge, pilot-announce, pilot-slack-bridge	Updates status page, sends incident notifications

Setup Procedure

Step 1: Ask the user which role this agent should play and what prefix to use.

Step 2: Install the skills for the chosen role:

# For monitor:
clawhub install pilot-health pilot-cron pilot-metrics

# For aggregator:
clawhub install pilot-event-filter pilot-dataset pilot-audit-log

# For publisher:
clawhub install pilot-webhook-bridge pilot-announce pilot-slack-bridge

Step 3: Set the hostname:

pilotctl --json set-hostname <prefix>-<role>

Step 4: Write the setup manifest:

mkdir -p ~/.pilot/setups
cat > ~/.pilot/setups/status-page.json << 'MANIFEST'
<role-specific manifest from templates below>
MANIFEST

Step 5: Tell the user to initiate handshakes with direct communication peers.

Manifest Templates Per Role

monitor

{"setup":"status-page","setup_name":"Status Page","role":"monitor","role_name":"Service Monitor","hostname":"<prefix>-monitor","description":"Pings endpoints, checks response times, detects outages and degradation.","skills":{"pilot-health":"Run HTTP/TCP health checks against configured service endpoints.","pilot-cron":"Schedule health checks at regular intervals (e.g. every 30 seconds).","pilot-metrics":"Track response times, error rates, and availability per service."},"peers":[{"role":"aggregator","hostname":"<prefix>-aggregator","description":"Receives health check results for status aggregation"}],"data_flows":[{"direction":"send","peer":"<prefix>-aggregator","port":1002,"topic":"health-check","description":"Per-service health check results"}],"handshakes_needed":["<prefix>-aggregator"]}

aggregator

{"setup":"status-page","setup_name":"Status Page","role":"aggregator","role_name":"Status Aggregator","hostname":"<prefix>-aggregator","description":"Combines health checks into overall system status, tracks uptime percentages, maintains incident history.","skills":{"pilot-event-filter":"Filter health events by severity and detect incident-worthy degradation.","pilot-dataset":"Store uptime history, incident records, and historical status snapshots.","pilot-audit-log":"Log all status transitions and incident lifecycle events for audit."},"peers":[{"role":"monitor","hostname":"<prefix>-monitor","description":"Sends health check results"},{"role":"publisher","hostname":"<prefix>-publisher","description":"Receives status updates and incident events"}],"data_flows":[{"direction":"receive","peer":"<prefix>-monitor","port":1002,"topic":"health-check","description":"Per-service health check results"},{"direction":"send","peer":"<prefix>-publisher","port":1002,"topic":"status-update","description":"System status updates and incident events"}],"handshakes_needed":["<prefix>-monitor","<prefix>-publisher"]}

publisher

{"setup":"status-page","setup_name":"Status Page","role":"publisher","role_name":"Status Publisher","hostname":"<prefix>-publisher","description":"Updates public status page, sends incident notifications to subscribers via email and Slack.","skills":{"pilot-webhook-bridge":"Push status updates and incident events to the public status page API.","pilot-announce":"Broadcast incident notifications to all registered subscribers.","pilot-slack-bridge":"Post incident updates and resolution notices to operations Slack channels."},"peers":[{"role":"aggregator","hostname":"<prefix>-aggregator","description":"Sends status updates and incident events"}],"data_flows":[{"direction":"receive","peer":"<prefix>-aggregator","port":1002,"topic":"status-update","description":"System status updates and incident events"},{"direction":"send","peer":"external","port":443,"topic":"incident-notification","description":"Incident notifications to subscribers"}],"handshakes_needed":["<prefix>-aggregator"]}

Data Flows

• monitor -> aggregator : health-check events (port 1002)
• aggregator -> publisher : status-update events (port 1002)
• publisher -> external : incident-notification via webhook (port 443)

Handshakes

# monitor <-> aggregator:
pilotctl --json handshake <prefix>-aggregator "setup: status-page"
pilotctl --json handshake <prefix>-monitor "setup: status-page"
# aggregator <-> publisher:
pilotctl --json handshake <prefix>-publisher "setup: status-page"
pilotctl --json handshake <prefix>-aggregator "setup: status-page"

Workflow Example

# On aggregator -- subscribe to health checks:
pilotctl --json subscribe <prefix>-monitor health-check
# On publisher -- subscribe to status updates:
pilotctl --json subscribe <prefix>-aggregator status-update
# On monitor -- publish a health check:
pilotctl --json publish <prefix>-aggregator health-check '{"service":"api-gateway","status":"degraded","response_ms":2340,"threshold_ms":500}'
# On aggregator -- publish status update:
pilotctl --json publish <prefix>-publisher status-update '{"overall_status":"degraded","incident":true,"incident_id":"INC-2025-0018","affected_services":["api-gateway"]}'

Dependencies

Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.