Agent skill

flyio-performance-tuning

Optimize Fly.io application performance with auto-stop/start tuning, VM sizing, multi-region latency optimization, and connection pooling. sizing". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flyio-performance-tuning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Version: 1.6.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(fly:*)
Requires: Designed for Claude Code
Path: plugins/saas-packs/flyio-pack/skills/flyio-performance-tuning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Fly.io Performance Tuning ## Overview Optimize Fly.io performance: eliminate cold starts, right-size VMs, leverage multi-region for low latency, and tune concurrency settings. ## Instructions ### Step 1: Eliminate Cold Starts ```toml # fly.toml — suspend instead of stop for faster resume (~100ms vs ~5s) [http_service] auto_stop_machines = "suspend" # Suspend to RAM, not full stop auto_start_machines = true min_machines_running = 1 # Always-warm in primary region # For latency-critical: keep machines running in all regions # min_machines_running applies globally ``` ### Step 2: Right-Size VMs ```bash # Check current allocation fly scale show -a my-app # Start small, scale up based on metrics fly scale vm shared-cpu-1x --memory 256 # Start here fly scale vm shared-cpu-1x --memory 512 # If memory-constrained fly scale vm shared-cpu-2x --memory 1024 # If CPU-bound fly scale vm performance-2x --memory 4096 # For compute-heavy workloads ``` | Workload | VM | Memory | When | |----------|-------|--------|------| | Static site / API proxy | shared-cpu-1x | 256mb | Low traffic | | Node.js API | shared-cpu-1x | 512mb | Most apps | | Heavy processing | shared-cpu-2x | 1gb | Background jobs |

What's inside
Steps it walks through
  1. Overview
  2. Instructions
  3. Step 1: Eliminate Cold Starts
  4. Step 2: Right-Size VMs
  5. Step 3: Multi-Region Latency Optimization
  6. Step 4: Connection Pooling for Postgres
  7. Step 5: Tune Concurrency
  8. Resources
  9. Next Steps
Commands it runs
Check current allocation
fly scale show -a my-app
Start small, scale up based on metrics
fly scale vm shared-cpu-1x --memory 256    # Start here
fly scale vm shared-cpu-1x --memory 512    # If memory-constrained
fly scale vm shared-cpu-2x --memory 1024   # If CPU-bound
fly scale vm performance-2x --memory 4096  # For compute-heavy workloads
Deploy close to your users
fly scale count 1 --region iad    # US East
fly scale count 1 --region lhr    # Europe
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the flyio-performance-tuning skill do?

Optimize Fly.io application performance with auto-stop/start tuning, VM sizing, multi-region latency optimization, and connection pooling. sizing". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flyio-performance-tuning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going