Agent skill · software engineering · jeremylongshore
flyio-hello-world
Prepare and verify a minimal Fly.io application launch with reviewable configuration and a safe first deployment. Use when onboarding a new service. Trigger with: "launch first Fly app", "deploy hello world to Fly", "create Fly launch plan".
Why this skill is useful
Adds executable scripts for deploying applications to Fly.io using both the flyctl CLI and the Machines API, which are not commonly found in public documentation.
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
First Fly.io App Launch Overview Create the smallest useful first deployment while keeping generated configuration reviewable. Start with one environment, one explicit region, a health endpoint, and no persistent data; add global placement or storage only after the base release is observable and repeatable. Prerequisites Application source, runtime port, startup command, and local health proof Organization, app naming policy, region choice, and cost owner Interactive identity for setup or a scoped token for approved automation Instructions Step 1: Inspect the application Identify build method, Dockerfile status, process command, listening address, internal port, health route, environment, and secret inputs. Step 2: Generate without deploying Use the provider launch flow with deployment disabled so fly.toml and any Dockerfile changes can be reviewed before resource creation. Step 3: Review the config Confirm app name, primary region, build source, process groups, service ports, health checks, VM size, autostart or autostop, and shutdown behavior. Step 4: Set secrets safely Store runtime credentials through Fly App secrets. Leave non-sensitive configuration in reviewed environment fields and exclude local secret files from source control. Step 5: Perform the approved first deploy Bind the source revision and image, use rolling behavior, and observe build, Machine creation, and health rather than assuming the public URL proves complete success. Step 6: Verify and document Check the endpoint, health status, Machine image and region, logs, restart behavior, and billable resources. Record teardown or ownership before handoff. Authentication Interactive onboarding can use fly auth login. Automation should use the narrowest expiring token exposed as FLYAPITOKEN or FLYACCESSTOKEN. Never copy the personal login token into CI. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-hello-world