fly-deploy

Deploy and manage Fly.io applications for Quipu Brain and Hands services.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/andy-austin/quipu --skill fly-deploy-andy-austin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fly-deploy
Source: https://github.com/andy-austin/quipu/tree/main/.claude/skills/fly-deploy
Command: npx skills add https://github.com/andy-austin/quipu --skill fly-deploy-andy-austin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy, manage, and troubleshoot Fly.io deployments for the Quipu project, covering Brain and Hands services. It helps teams deploy to public and internal networks, configure secrets, scale resources, and monitor health.

Core Features & Use Cases

  • Deploy both Brain (public) and Hands (internal) Fly.io apps
  • Manage secrets and environment configuration across apps
  • Monitor logs, scale machines, and troubleshoot networking

Quick Start

Provide your Fly.io targets and secrets, then initiate the deployment workflow to deploy both Brain and Hands to Fly.io.

Frequently Asked Questions about fly-deploy

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

FAQPage Schema
How do I deploy a Fly.io app to both public and internal networks?

Deploy Fly.io apps to public and internal networks by configuring separate Brain and Hands services, then initiating the deployment workflow to push both services with distinct network visibility settings.

What's the best way to manage secrets across multiple Fly.io applications?

Manage Fly.io secrets across multiple applications by using flyctl to configure environment variables and secrets for each app, ensuring Brain and Hands services receive their specific configuration values.

How do I scale Fly.io machines and monitor logs for production troubleshooting?

Scale Fly.io machines and monitor production logs by using flyctl commands to adjust machine counts and stream application logs, enabling health monitoring and troubleshooting for deployed services.

Do I need a Fly.io account and flyctl installed before deploying my application?

Yes, deploying Fly.io applications requires a Fly.io account, the Fly CLI (flyctl) installed locally, and project configuration files prepared before initiating the deployment workflow for Brain and Hands services.

Why does my Fly.io deployment fail when configuring internal network services?

Fly.io deployment failures for internal network services often stem from misconfigured project settings or missing secrets, requiring troubleshooting of flyctl configuration and verification of Hands service network parameters.

Can I use flyctl to troubleshoot networking issues across Brain and Hands services?

Yes, use flyctl to troubleshoot networking issues across Brain and Hands services by monitoring logs, checking machine health, and verifying internal and public network configurations during deployment.