Agent skill · software engineering · jeremylongshore
flyio-ci-integration
Design a least-privilege Fly.io CI lane with deterministic validation, deployment, and rollback evidence. Use when wiring or auditing automated deployments. Trigger with: "add Fly.io CI", "harden Fly deploy workflow", "rotate Fly CI token".
Why this skill is useful
Provides specific CI/CD pipeline configurations and deployment workflows for Fly.io that the AI wouldn't reliably generate on its own.
What it needs
Requires docker installed locally. Requires fly.io, github 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 CI Deployment Control Overview Build CI as a controlled release system rather than a single deploy command. Separate pull-request validation from authenticated deployment, bind production to an immutable revision, and retain enough evidence to identify and reverse the release. Prerequisites Named app, organization, environment, release owner, and rollback owner Protected CI environment with an approved secret manager Health endpoint or other deployment check and a tested prior release Instructions Step 1: Separate validation from deployment Run secret-free configuration, container, and contract checks on pull requests. Permit authenticated Fly.io access only in a protected post-merge or manually approved environment. Step 2: Issue the narrowest token Use an app-scoped deploy token for one app, an organization token only for approved multi-app workflows, or a read-only token for observation. Set an explicit expiry and store only the secret reference. Step 3: Pin the release inputs Bind source commit, image digest, flyctl setup action or binary version, target app, configuration hash, and deployment strategy before execution. Step 4: Validate the candidate Check the rendered app configuration, image startup contract, health checks, release command, volume constraints, and rollback target without changing production. Step 5: Deploy through one serialized lane Use environment concurrency so two production releases cannot race. Capture the release identifier and wait for health checks rather than treating command exit alone as success. Step 6: Verify and close Probe the approved endpoint, inspect aggregate health and Machine state, reconcile the running image, and either record success or invoke the tested rollback. Authentication Expose the token to the deployment step as FLYAPITOKEN or FLYACCESSTOKEN only. The provider recommends scoped tokens created with fly tokens create; do not use the deprecated hidden fly auth token output in CI. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-ci-integration