sb-dev/openquant / .agents/skills/fly
fly
FlaggedOperate Fly.io: sign in or sign up, launch and deploy apps, edit fly.toml, scale Machines across regions, manage volumes, secrets, IP addresses, certificates and custom domains, Managed Postgres, Tigris object storage and Upstash Redis, read logs and status, troubleshoot failed deploys and health checks, and run builds, tests or agents in Sprites, Fly's persistent remote Linux environments. Use this skill whenever the user mentions Fly, Fly.io, flyctl, fly.toml, Machines, deploying, scaling, regions, volumes, secrets, Postgres or MPG on Fly, Sprites, sprite-env, sprites.dev, a sandbox or remote build environment, or infrastructure operations, even if they don't say "Fly" explicitly. Also invoke it to set up Fly agent tooling (skills, MCP, login) or when the user asks to be signed up or onboarded.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.1 KB |
| references/configure.md | markdown | 9.4 KB |
| references/deploy.md | markdown | 7.1 KB |
| references/launch.md | markdown | 5.4 KB |
| references/machines.md | markdown | 6.6 KB |
| references/networking.md | markdown | 5.9 KB |
| references/operate.md | markdown | 6.7 KB |
| references/postgres.md | markdown | 6.6 KB |
| references/safety.md | markdown | 6.0 KB |
| references/scale.md | markdown | 5.3 KB |
| references/secrets.md | markdown | 3.9 KB |
| references/setup.md | markdown | 6.8 KB |
| references/sprites-cli.md | markdown | 9.3 KB |
| references/sprites.md | markdown | 17.4 KB |
| references/storage.md | markdown | 3.1 KB |
| references/tools.md | markdown | 14.4 KB |
| references/volumes.md | markdown | 4.6 KB |
references/storage.md
View on GitHub# Object storage, Redis, and extensions
Fly provisions several partner-run services through flyctl. Each creates a
billable resource in the partner's system, bound to your org, and usually
sets secrets on an app. Confirm the org, region and plan before creating, and
read each command's `--help`; partner flags change.
## Tigris object storage (`fly storage`)
S3-compatible, globally distributed buckets.
```bash
fly storage list [-o <org>]
fly storage create -n <bucket> -o <org> [-a <app>] [--public]
fly storage status <bucket>
fly storage update <bucket> [--public|--private] ...
fly storage dashboard <bucket>
fly storage destroy <bucket> [-y] # deletes the bucket and every object
```
`create` with `-a <app>` sets `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`,
`AWS_ENDPOINT_URL_S3`, `AWS_REGION` and `BUCKET_NAME` on the app as secrets.
Any S3 client works against the endpoint. Shadow-bucket flags
(`--shadow-endpoint`, `--shadow-name`, ...) migrate from an existing S3
bucket; they take credentials, so take them from the user's environment
rather than chat. `[[statics]] tigris_bucket` in `fly.toml` serves a bucket
through the proxy ([configure.md](configure.md)). `fly launch` offers a
bucket; `--no-object-storage` skips it.
## Upstash Redis (`fly redis`)
```bash
fly redis plans
fly redis list [-o <org>]
fly redis create -n <name> -o <org> -r <region> [--plan <plan>] [--replica-regions ams,syd] [--no-replicas] [--enable-eviction]
fly redis status <name>
fly redis connect <name> # redis-cli
fly redis proxy <name> # local port
fly redis update <name> ...
fly redis reset <name> # new password; breaks existing connections
fly redis destroy <name> # irreversible
fly redis dashboard
```
The connection URL is shown at creation and in `status`; set it on the app as
`REDIS_URL` with `fly secrets set` without echoing it. Read replicas are per
region; the primary region should match the app's `primary_region`.
## Other extensions (`fly extensions`)
```bash
fly extensions sentry create -a <app> # Sentry project; sets SENTRY_DSN
fly extensions arcjet ... # bot protection and rate limiting
fly extensions wafris ... # WAF
fly extensions vector ... # Upstash Vector index
fly extensions kubernetes ... # Fly Kubernetes clusters
fly extensions storage ... # alias of fly storage
```
Each has `create`, `list`, `status`, `destroy`, `dashboard` and often
`update`. They may prompt to accept the partner's terms in the browser; let
the user do that.
## Monitoring add-ons
`fly dashboard -a <app>` opens the app in the web UI; `fly dashboard metrics`
opens Grafana. `[[metrics]]` in `fly.toml` exposes a Prometheus endpoint Fly
scrapes. `fly synthetics` manages synthetic monitoring; `fly incidents` lists
platform incidents affecting your apps; `fly platform status` shows platform
health.
## Over MCP
None of these partner resources are exposed through the Fly MCP server. Use
flyctl, and say so if asked.
Checked against flyctl v0.4.123 on 2026-10-28.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |