Agent skill · software engineering · jeremylongshore
flyio-webhooks-events
Detect Fly.io Machine, health, release, and log changes through supported reads, waits, and log export without claiming general app webhooks. Use when building operational event automation. Trigger with: "monitor Fly Machine changes", "replace Fly webhook", "stream Fly health events".
Why this skill is useful
Adds specific commands and patterns for monitoring and processing Fly.io machine events that the AI wouldn't reliably generate on its own.
What it needs
Requires fly, jq installed locally. Requires fly.io account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fly.io Machine and Health Change Feed Overview The general app platform does not document a customer-configurable webhook subscription and signing surface, so this route uses supported change detection through Machines reads and state waits, health status, deployment evidence, and documented log shipping. Extension-provider machine-event webhooks are a separate partner-specific contract and are not assumed here. Prerequisites Selected signal types, apps, regions, process groups, and service objectives Durable last-seen state, deduplication key, overlap policy, and sink acknowledgement Read-only token and redaction rules for Machine, health, release, and log fields Instructions Step 1: Choose supported signals Use Machine list or get for inventory, the Machine wait endpoint for a known transition, health-check status for routing readiness, release evidence for deployments, and documented log shipping for application events. Step 2: Snapshot the starting boundary Record active Machine ID and instance version, lifecycle state, image, checks, regions, and the observation-window checkpoint before polling. Step 3: Normalize change identity Create a deterministic key from app, Machine, instance version, signal type, observed transition, and source timestamp. Preserve provider request or release lineage. Step 4: Deduplicate before publishing Compare with last-seen state and the sink acknowledgement store. Publish only changed, validated, redacted records and advance the checkpoint after acknowledgement. Step 5: Detect gaps and stale monitors Alert on missed polls, wait timeouts, health age, log-export lag, state discontinuities, and unknown instance replacement. Re-read authoritative state before replay. Step 6: Reconcile downstream action Operational events may recommend but must not automatically restart, scale, or delete resources without a separately approved control policy. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-webhooks-events