Agent skill · data analytics · jeremylongshore
flyio-common-errors
Diagnose Fly.io deployment, routing, health, Machine, volume, and private-network failures with evidence-first triage. Use when an app is unhealthy or a release stalls. Trigger with: "debug Fly deploy", "why is my Fly app down", "triage Fly Machine".
Why this skill is useful
Provides specific commands and troubleshooting steps for Fly.io deployment errors that the AI wouldn't reliably generate on its own.
What it needs
Requires fly installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fly.io Failure Triage Overview Classify the failing layer before changing anything. Separate local build failures, release orchestration, Machine lifecycle, Fly Proxy routing, private DNS, volume placement, and application behavior so remediation does not destroy the evidence. Prerequisites App and environment identifiers plus incident start time Last known healthy release, image, configuration, and region placement Read-only access to health, Machine, release, volume, and log evidence Instructions Step 1: Freeze the incident window Record the symptom, first observation, affected regions, recent release or secret changes, and the last known healthy revision. Step 2: Validate configuration and release identity Compare the deployed image and rendered configuration with the intended release. Check process groups, ports, services, health paths, signals, and timeouts. Step 3: Inspect health and Machine lifecycle Distinguish a failed health check from a Machine that is stopped, suspended, replacing, or repeatedly restarting. Preserve instance-version information. Step 4: Check routing and networking Verify public allocation, Fly Proxy service configuration, listening address, target port, and private .internal DNS semantics. Remember that stopped Machines are absent from AAAA responses. Step 5: Check regional storage dependencies Confirm that any attached volume exists in the same region and is mounted at the expected path. Treat a single volume as a single-host durability boundary. Step 6: Choose the smallest recovery Prefer rollback, configuration correction, or one bounded Machine action over fleet-wide restart. Reconcile health and image state after recovery. Authentication Use a read-only organization token for observation where possible. A deploy-capable identity can change code and therefore reach runtime secrets; keep diagnostic access separate from mutation authority and never paste tokens into incident records. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-common-errors