skills.rest
kaiohenricunha
kaiohenricunhaCOMMUNITY
Explore all skills by this author →
𝕏@kaiohenricunhaGitHub

flyctl

Enforce operator confirmation gates for Fly.io infrastructure mutations.

Updated Apr 14, 2026
Search Tags:#devops#deployment#infrastructure#secrets-management#health-checks#flyio#machine-scaling
One-click install
npx skills add https://github.com/kaiohenricunha/dotbabel --skill flyctl-kaiohenricunha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flyctl
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/flyctl
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill flyctl-kaiohenricunha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of accidental, unapproved mutations to Fly.io infrastructure during AI-assisted workflows by enforcing explicit operator invocation and mandatory confirmation gates for all production-side-effect operations.

Core Features & Use Cases

  • Explicit invocation only: Prevents the AI from auto-routing phrases like "deploy to Fly" to this skill, requiring operators to type /flyctl <subcommand> directly for all actions.
  • Production safety rails: Enforces typed app-name confirmation for all destructive operations on production apps, with a deliberate --no-confirm flag for known non-production use cases.
  • Comprehensive Fly operations: Supports deploying apps (with image reference validation), tailing logs, managing secrets, inspecting and scaling machines, SSH access, proxying internal services, and running health checks, with automatic app discovery from fly.toml.
  • Use Case: A DevOps operator can safely scale a production Fly app to 3 machines by running /flyctl scale count 3, with the skill automatically detecting the app from fly.toml, prompting for app name confirmation, and verifying the new machine layout after the operation.

Quick Start

Use the flyctl skill to deploy your latest pre-built container image to your Fly.io app, following the prompted app name confirmation for production environments.

Frequently Asked Questions about flyctl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely deploy a pre-built container image to Fly.io using AI workflows without accidental mutations?▼

You can deploy pre-built container images to Fly.io safely by invoking the flyctl wrapper, which validates image references and requires explicit operator confirmation gates before executing any production-side-effect operations.

Can I scale Fly.io machines in production without risking unintended infrastructure changes?▼

Yes, scaling Fly.io machines requires typed app-name confirmation for production apps, automatically discovering the app context from fly.toml and verifying the new machine layout after the operation completes.

How do I prevent an AI assistant from auto-routing commands to Fly.io infrastructure operations?▼

Prevent auto-routing by requiring explicit operator invocation; the flyctl skill refuses to auto-execute mutating commands from phrases like deploy to Fly, requiring operators to type the subcommand directly.

What Fly.io DevOps operations are supported for infrastructure management and log triage?▼

Supported Fly.io operations include deploying apps, tailing logs, managing secrets, inspecting and scaling machines, SSH access, proxying internal services, and running health check verification.

Does the flyctl skill require a fly.toml file to manage Fly.io app deployments and secrets?▼

The flyctl skill auto-discovers app context from fly.toml, using it to identify the target application for deployments, secret management, and machine scaling operations without manual app specification.

What are the limitations when using AI-assisted workflows for Fly.io infrastructure mutations?▼

The flyctl skill refuses to execute mutating commands without explicit operator approval for production apps, enforcing a deliberate confirmation gate that cannot be bypassed unless the non-production flag is used.

Related Skills

Explore More Software Engineering Skills→
mauromeddamauromedda
13

trivy

Scan filesystems, images, and IaC files for CRITICAL and HIGH vulnerabilities before deployment.

Community
Advanced
hathbangerhathbanger

fly-deploy

Automate Fly.io deployment management with flyctl subcommands.

Community
Advanced
erfianugraherfianugrah
1

fly

Manage Fly.io app lifecycle operations via the flyctl CLI.

Community
Advanced
mgd34msumgd34msu
4

fly-io

Deploy and manage applications on Fly.io using the flyctl CLI.

Community
Intermediate