flyio-cli

What This Skill Does

The flyio-cli skill provides the OpenClaw agent with full access to the Fly.io command-line interface (flyctl). This empowers the agent to assist with the entire lifecycle of a cloud-native application, from initial status checks and log streaming to complex deployments and database management. The skill is designed with a strict safety-first hierarchy, ensuring that read-only diagnostics are performed freely, while any state-changing operations—such as deployments, secret rotation, or infrastructure scaling—require explicit user confirmation before execution.

Installation

To enable this skill in your OpenClaw environment, execute the following command in your terminal or agent configuration prompt: clawhub install openclaw/skills/skills/justinburdett/flyio-cli

Use Cases

This skill is highly effective for developers hosting Rails, Node.js, or Go applications on Fly.io. It is particularly useful for:

• Observability: Quickly diagnosing runtime errors by tailing logs or inspecting app configuration.
• Deployment Automation: Managing the deployment flow, especially when debugging build failures related to Dockerfiles or platform mismatches.
• Infrastructure Management: Attaching Postgres clusters to applications, managing environment secrets, and scaling machine resources.
• CI/CD Integration: Setting up and debugging GitHub Actions workflows for production deployments or ephemeral preview apps for pull requests.

Example Prompts

1. "Check the current status and logs for the 'prod-api' app; are there any recent crash loops or health check failures?"
2. "I'm getting a 'Bundler can't find platform' error during my build. Can you check my Gemfile.lock and suggest how to fix it for the Fly.io environment?"
3. "Please attach the existing postgres-cluster-01 to my staging-app, then verify that the database is reachable via psql."

Tips & Limitations

• Safety Protocol: Always prefer read-only commands (status, logs, config, list) when investigating. If an operation changes the state of your infrastructure (e.g., fly deploy, fly secrets set), the agent will pause to ask for your consent.
• Debugging Builds: If a build fails, start by running fly deploy --verbose. Check the Dockerfile to ensure the runtime version matches your local .ruby-version or package.json.
• Postgres Management: When working with Postgres, ensure you are targeting the correct DB app. Use fly postgres list to confirm your target names before attempting to modify configurations or create new databases.