Fly.io CLI
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is a coherent Fly.io operations helper that defaults to read-only diagnostics and requires user approval before production-changing actions, though users should treat Fly tokens and deploy/database/secrets commands carefully.
Use this skill only while targeting the intended Fly.io account and app. Let it start with read-only status, logs, config, and release checks; explicitly approve any deploy, SSH exec, secret change, scaling, machine, volume, or Postgres operation only after reviewing the exact command and target. Protect any FLY_API_TOKEN used in GitHub Actions and keep preview automation scoped to preview apps and databases.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user approves the wrong command or target app, the agent could change production deployments, secrets, databases, or server state.
The skill documents broad Fly.io operational authority, including deploys, SSH exec, and secrets changes, but it also clearly gates those actions behind explicit user approval.
These commands can execute arbitrary code on servers or mutate production state. Only run them when the user explicitly asks you to.
Before approving any state-changing command, confirm the Fly account, app name, exact command, expected impact, and rollback plan; use read-only diagnostics first.
A Fly token stored in GitHub Actions may allow deployments or other Fly resource changes if it is over-scoped, exposed, or used by an unsafe workflow.
The GitHub Actions guidance introduces a Fly API token for deployment workflows; this is expected for Fly.io automation but represents delegated account authority.
Secrets: - `FLY_API_TOKEN`
Store the token only as a protected GitHub secret, use the least privilege available, prefer test/dummy secrets for previews, and rotate the token if exposure is suspected.