How do I install the Fly Deploy skill?

Run npx skillmds@latest add diegosouzapw/fly-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fly Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fly Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fly Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fly Deploy?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fly Deploy by diegosouzapw — Agent Skill

Name: Fly Deploy
Rating: 4.666666666666667 (3 reviews)
Author: diegosouzapw

Fly Deploy

Deploy applications to Fly.io using flyctl. Handles project detection, fly.toml generation, secrets configuration, and deployment. Use when deploying apps to Fly.io, creating fly.toml files, debugging Fly.io deployment failures, or configuring Fly.io services.

diegosouzapw Updated Sep 8, 2026 54 repo stars

File contents

Fly.io Deployment

Deploy applications to Fly.io from source code or Docker images.

Prerequisites

Ensure flyctl is installed and authenticated:

# Check installation
fly version

# Authenticate if needed
fly auth login

Deployment Workflow

1. Detect Project Type

Examine the project root to determine the stack:

Indicator	Type	Reference
`next.config.*`	Next.js	references/nextjs.md
`Dockerfile`	Docker	references/docker.md
`package.json` (no Next)	Node.js	references/nodejs.md
`requirements.txt` / `pyproject.toml`	Python	references/python.md
`index.html` only	Static	references/static.md

Read the appropriate reference file for framework-specific configuration.

2. Initialize or Configure

New app:

fly launch --no-deploy

This creates fly.toml. Review and adjust before deploying.

Existing app (no fly.toml):

fly launch --no-deploy
# Or create fly.toml manually using references/fly-toml.md

3. Set Secrets

Set environment variables that shouldn't be in fly.toml:

# Single secret
fly secrets set DATABASE_URL="postgres://..."

# Multiple secrets
fly secrets set KEY1=value1 KEY2=value2

# From .env file
cat .env | fly secrets import

Secrets trigger a redeploy. Use --stage to batch them:

fly secrets set --stage KEY1=value1
fly secrets set --stage KEY2=value2
fly secrets deploy

4. Deploy

fly deploy

Common flags:

--ha — High availability (2+ machines, default)
--no-ha — Single machine (dev/staging)
--strategy rolling|bluegreen|canary|immediate
--wait-timeout 5m — Extend for slow builds

5. Verify

# Check status
fly status

# View logs
fly logs

# Open in browser
fly open

Troubleshooting

If deployment fails, consult references/troubleshooting.md for common errors and fixes.

Quick checks:

Health check passing? Check internal_port matches app's listen port
App starting? Check fly logs for crash loops
Build failing? Check Dockerfile or buildpack compatibility

Configuration Reference

For detailed fly.toml options, see references/fly-toml.md.

Key settings:

primary_region — Where machines deploy by default
[http_service] — HTTP/HTTPS configuration
[env] — Non-sensitive environment variables
[[vm]] — CPU/memory sizing

---name: fly-deploydescription: Deploy applications to Fly.io using flyctl. Handles project detection, fly.toml generation, secrets configuration, and deployment. Use when deploying apps to Fly.io, creating fly.toml files, debugging Fly.io deployment failures, or configuring Fly.io services.---# Fly.io DeploymentDeploy applications to Fly.io from source code or Docker images.## PrerequisitesEnsure `flyctl` is installed and authenticated:```bash# Check installationfly version# Authenticate if neededfly auth login```## Deployment Workflow### 1. Detect Project TypeExamine the project root to determine the stack:| Indicator | Type | Reference ||-----------|------|-----------|| `next.config.*` | Next.js | [references/nextjs.md](references/nextjs.md) || `Dockerfile` | Docker | [references/docker.md](references/docker.md) || `package.json` (no Next) | Node.js | [references/nodejs.md](references/nodejs.md) || `requirements.txt` / `pyproject.toml` | Python | [references/python.md](references/python.md) || `index.html` only | Static | [references/static.md](references/static.md) |Read the appropriate reference file for framework-specific configuration.### 2. Initialize or Configure**New app:**```bashfly launch --no-deploy```This creates `fly.toml`. Review and adjust before deploying.**Existing app (no fly.toml):**```bashfly launch --no-deploy# Or create fly.toml manually using references/fly-toml.md```### 3. Set SecretsSet environment variables that shouldn't be in fly.toml:```bash# Single secretfly secrets set DATABASE_URL="postgres://..."# Multiple secretsfly secrets set KEY1=value1 KEY2=value2# From .env filecat .env | fly secrets import```Secrets trigger a redeploy. Use `--stage` to batch them:```bashfly secrets set --stage KEY1=value1fly secrets set --stage KEY2=value2fly secrets deploy```### 4. Deploy```bashfly deploy```**Common flags:**- `--ha` — High availability (2+ machines, default)- `--no-ha` — Single machine (dev/staging)- `--strategy rolling|bluegreen|canary|immediate`- `--wait-timeout 5m` — Extend for slow builds### 5. Verify```bash# Check statusfly status# View logsfly logs# Open in browserfly open```## TroubleshootingIf deployment fails, consult [references/troubleshooting.md](references/troubleshooting.md) for common errors and fixes.**Quick checks:**1. Health check passing? Check `internal_port` matches app's listen port2. App starting? Check `fly logs` for crash loops3. Build failing? Check Dockerfile or buildpack compatibility## Configuration ReferenceFor detailed fly.toml options, see [references/fly-toml.md](references/fly-toml.md).**Key settings:**- `primary_region` — Where machines deploy by default- `[http_service]` — HTTP/HTTPS configuration- `[env]` — Non-sensitive environment variables- `[[vm]]` — CPU/memory sizing

Frequently asked questions