# Flyio

> Fly.io integration for application monitoring, machine lifecycle management, metrics, logs, and incident remediation

- Skill: `arvo-ai/flyio` (Agent Skill)
- Install (CLI): `npx skillmds@latest add arvo-ai/flyio`
- Raw SKILL.md: https://api.skillmd.com/api/skills/arvo-ai/flyio/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Arvo-AI (https://skillmd.com/u/arvo-ai)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/arvo-ai/flyio

---


# Fly.io Integration

## Overview
Fly.io is connected for application monitoring, machine lifecycle management, and incident remediation.

## Instructions

### How to interact
- Use `cloud_exec('flyio', '<fly command>')` for all Fly.io CLI operations.
- The CLI (`flyctl`) is pre-authenticated with the user's org-scoped token.
- Always pass `--json` flag for structured output when available.

### Prometheus metrics
Use `query_flyio_metrics(query)` for PromQL queries against Fly.io's Prometheus federation. Common metrics include (but are not limited to) `fly_instance_up`, `fly_instance_cpu`, `fly_instance_memory_resident`, `fly_edge_http_responses_count`, `fly_edge_http_response_time_seconds_bucket`, `fly_instance_net_recv_bytes`, `fly_app_concurrency`.

### Critical rules
- Always use `cloud_exec('flyio', ...)` -- never call the REST API directly.
- Use `-a <app_name>` for commands that target a specific app (e.g. `fly status -a myapp`). Do NOT use `-a` on global commands like `fly apps list`, `fly regions list`.
- Pass `--json` for structured output when available (not all commands support it -- if it fails, retry without).
- For logs, always use `--no-tail` to avoid indefinite streaming (e.g. `fly logs -a myapp --no-tail`).