Agent skill · software engineering · jeremylongshore
flyio-prod-checklist
Gate a Fly.io production release across ownership, configuration, identity, health, capacity, data, observability, cost, and rollback. Use when reviewing a first launch or material change. Trigger with: "review Fly production readiness", "approve Fly launch", "run Fly go-live checklist".
Why this skill is useful
Adds a comprehensive checklist and executable validation script for Fly.io production deployments that aren't widely documented.
What it needs
Requires bash installed locally. Requires fly.io account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fly.io Production Readiness Gate Overview Make go-live a signed evidence boundary. The gate must cover the actual workload: stateless Machines, region-bound volumes, Managed Postgres, release commands, health semantics, autostart, networking, observability, billing, and tested rollback. Prerequisites Business, technical, security, data, support, and rollback owners Immutable candidate image and reviewed configuration Load, failure, restore, deployment, and rollback evidence from a representative environment Instructions Step 1: Confirm ownership and scope Record app, organization, environment, domains, regions, process groups, data stores, objectives, on-call route, and accepted risks. Step 2: Review identity and secrets Use scoped expiring tokens, protect production environments, inspect secret names and digests without values, and prove rotation and revocation. Step 3: Review runtime and deployment Validate image, architecture, ports, processes, signals, release command, health checks, strategy, unavailable capacity, and volume compatibility. Step 4: Review resilience and data Confirm Machine redundancy where required, regional placement, dependency failure behavior, Managed Postgres or volume backup boundaries, restore tests, and reconciliation. Step 5: Review observability and cost Prove logs, metrics, health, alerts, provider-status escalation, resource inventory, cost owner, and cleanup of obsolete billable resources. Step 6: Exercise launch and rollback Run the approved release path, observe acceptance gates, restore the prior image or config in a drill, and close only after actual fleet reconciliation. Authentication Production deploy uses the narrowest app or organization token in a protected environment. Read-only monitoring should not share deploy authority. Remember that anyone with deploy access can deploy code that reads runtime App secrets. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-prod-checklist