Agent skill · marketing growth · jeremylongshore
flyio-cost-tuning
Analyze Fly.io Machine, volume, network, IP, and Managed Postgres cost drivers without freezing volatile prices. Use when reducing spend or forecasting capacity. Trigger with: "audit Fly bill", "right-size Fly Machines", "reduce Fly idle cost".
Why this skill is useful
Provides specific commands and strategies for optimizing costs on Fly.io that the AI wouldn't reliably generate on its own.
What it needs
Requires jq 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 Cost and Capacity Review Overview Optimize from measured usage and the current pricing page, not copied monthly constants. Separate running and stopped Machine charges, persistent volume and snapshot charges, network and IP costs, and Managed Postgres resources that live outside application deletion. Prerequisites Billing window, currency, organization, apps, and cost owner Machine state and resource history plus traffic, latency, and availability objectives Inventory of volumes, snapshots, IPs, transfer, builders, and Managed Postgres clusters Instructions Step 1: Reconcile the bill to resources Map each charge class to current Machines, volumes, snapshots, addresses, transfer, builders, and databases. Include unattached and stopped-resource dependencies. Step 2: Measure utilization and state Compare CPU, memory, concurrency, request, latency, restart, and running-time signals with the selected VM size and Machine count. Step 3: Evaluate autostop safely For eligible service apps, model autostopmachines as stop or suspend with autostartmachines and a deliberate minimum-running setting. Include cold-start and state-safety costs. Step 4: Right-size and place Change one dimension at a time: VM preset, additional memory, count, region placement, or database plan. Preserve capacity and recovery headroom. Step 5: Remove orphaned cost with approval Identify unattached volumes, obsolete snapshots beyond policy, unused addresses, old builders, and databases no longer referenced. Deletion requires owner confirmation and recovery evidence. Step 6: Verify savings and service health Compare the next billing interval and performance signals with the baseline; reverse changes that violate latency, availability, or recovery objectives. Authentication Prefer read-only organization tokens for inventory and billing analysis. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flyio-cost-tuning