Agent skill · software engineering · jeremylongshore
flyio-core-workflow-a
Operate a Fly.io application release from configuration review through deploy, scale, secret change, and rollback. Use when shipping or changing a Fly Launch app. Trigger with: "deploy Fly app", "scale Fly Machines", "roll back Fly release".
Why this skill is useful
Adds specific commands and configurations for deploying and managing applications on Fly.io that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, flyctl 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 Application Release Lifecycle Overview Treat the app release as a state transition with explicit configuration, image, capacity, health, and rollback boundaries. Fly Launch manages Machines from fly.toml, but production success still requires reconciliation against the running fleet. Prerequisites Source revision, image build contract, app name, environment, and primary region Reviewed fly.toml with process groups, services, health checks, and shutdown settings Approved deploy strategy, capacity envelope, secret plan, and rollback target Instructions Step 1: Inventory the current app Record current release, running image, Machine counts and regions, health, IP allocation, secrets digests, and attached storage. Step 2: Render the desired state Review build, process groups, services, concurrency, autostart or autostop, VM resources, regions, mounts, release command, and deployment policy. Step 3: Stage secrets separately Use Fly secrets rather than plaintext [env] values. Decide whether a secret change should restart Machines immediately or be staged for the release. Step 4: Select the deployment strategy Use rolling by default. Use canary only when temporary extra capacity is valid and no Machine volume blocks it; use blue-green only with health checks and compatible stateless capacity. Step 5: Deploy and wait Bind the release to an immutable image, observe replacement, and wait for health and Machine convergence. Do not infer success from image push alone. Step 6: Reconcile or roll back Compare desired and actual image, count, regions, health, and service behavior. Roll back if acceptance criteria or error budgets fail. Authentication Use an app-scoped deploy token for a single app and a short-lived organization token only when the operation legitimately spans apps. Fly App secrets are encrypted at rest but become environment variables inside Machines; anyone with deploy access can deploy code that reads them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-core-workflow-a