Agent skill

Flyio Upgrade Migration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Migrate Fly.io app configuration, runtime images, Machine resources, regions, volumes, or Managed Postgres through staged change control.

MITAuto-check passedDatabases

Install Flyio Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill flyio-upgrade-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace flyio-upgrade-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/flyio-upgrade-migration .claude/skills/flyio-upgrade-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
flyio-upgrade-migration
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
535 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Migrate Fly.io app configuration, runtime images, Machine resources, regions, volumes, or Managed Postgres through staged change control.

  • Works in 6 steps: Classify the change surface → Freeze current state and contract → Build a staging rehearsal → …
  • Upgrading a live workload
  • SKILL.md covers Overview, Prerequisites, Instructions and Authentication, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flyio Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Migrate Fly.io app configuration, runtime images, Machine resources, regions, volumes, or Managed Postgres through staged change control. Use when upgrading a live workload. Trigger with: "upgrade Fly app", "migrate Fly region", "change Fly runtime safely".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Requires current and target contracts, an immutable backup or export where data is involved, a representative staging boundary, and approved rollback criteria.

It sits in Databases. It works with PostgreSQL. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Upgrading a live workload
  • With: upgrade Fly app
  • Migrate Fly region
  • Change Fly runtime safely

Example prompts

  • “upgrade Fly app”
  • “migrate Fly region”
  • “change Fly runtime safely”
  • “/flyio-upgrade-migration”

Requirements

  • Compatibility (from SKILL.md): Requires current and target contracts, an immutable backup or export where data is involved, a representative staging boundary, and approved rollback criteria.
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Classify the change surface
  2. Freeze current state and contract
  3. Build a staging rehearsal
  4. Plan data movement explicitly
  5. Canary the approved change
  6. Complete or reverse

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • fly.io
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires current and target contracts, an immutable backup or export where data is involved, a representative staging boundary, and approved rollback criteria.

    From compatibility in the SKILL.md frontmatter.

Context cost

Flyio Upgrade Migration loads about 1.3k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 535 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 535 words, ~1,309 tokens.

Download SKILL.mdSave it as .claude/skills/flyio-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
flyio-upgrade-migration
description
Migrate Fly.io app configuration, runtime images, Machine resources, regions, volumes, or Managed Postgres through staged change control. Use when upgrading a live workload. Trigger with: "upgrade Fly app", "migrate Fly region", "change Fly runtime safely".
allowed-tools
Read, Grep, Write, Edit
compatibility
Requires current and target contracts, an immutable backup or export where data is involved, a representative staging boundary, and approved rollback criteria.
version
2.0.0
argument-hint
[app-change-source-and-target]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, flyio, migration, upgrade, change-control

Fly.io Runtime and Platform Change Control

Overview

Replace the obsolete Apps v1-to-v2 tutorial with ongoing change control for the current Machines platform. Treat flyctl, fly.toml, images, architecture, Machine resources, regions, volumes, and Managed Postgres as separate migration surfaces with distinct rollback and data risks.

Prerequisites

  • Current and target versions, configuration, image, architecture, resources, regions, and data topology
  • Provider documentation and release notes retrieved at the change boundary
  • Backup, export, restore test, acceptance gates, owner, approver, and rollback window

Instructions

Step 1: Classify the change surface

Separate CLI behavior, config schema, API contract, image or runtime, CPU architecture, VM size, region placement, volume state, and Managed Postgres changes.

Step 2: Freeze current state and contract

Record flyctl version, image, Machine instance versions, configuration hash, health, regions, volumes and snapshots, database plan and version, and dependency compatibility.

Step 3: Build a staging rehearsal

Use production-like configuration with synthetic or protected copied data. Exercise application startup, release command, health, connectivity, schema compatibility, and restore.

Step 4: Plan data movement explicitly

For a region-bound volume, create and verify the supported copy or snapshot path before Machine movement. For Managed Postgres, follow its current service features and support path; do not apply unmanaged Postgres commands.

Step 5: Canary the approved change

Change one process group, Machine, or non-production database boundary first. Observe health, errors, latency, data counts, and dependent services for the agreed window.

Step 6: Complete or reverse

Roll through remaining resources only after acceptance. Reconcile every image, instance version, region, volume attachment, and data count; retain rollback assets until expiry.

Authentication

Use a scoped deploy identity for app or Machine changes and a separate least-privilege database identity for data verification. Upgrade work does not authorize exposing snapshots, connection strings, or customer data to local or unapproved systems.

Show full SKILL.md (241 more words)Show less

Tool Discipline

Use Read and Grep to inspect application configuration, deployment evidence, provider documentation, fixtures, logs, schemas, and existing tests before proposing a change. Use Write or Edit only for an approved plan, configuration, implementation, test, or redacted receipt. Do not create, deploy, scale, restart, stop, suspend, destroy, rotate, revoke, expose, or migrate live Fly.io resources without explicit operator approval.

Output

  • Current-to-target contract and compatibility matrix
  • Staging, backup, restore, canary, rollout, reconciliation, and rollback plan
  • Migration receipt with resource versions, data evidence, exceptions, and rollback-asset expiry

Return the target organization, app, environment, region set, Machine or database identifiers, source-contract fingerprint, evidence, unresolved risks, rollback state, and final decision without exposing tokens, secrets, connection strings, or customer data.

Examples

An app moves to a new runtime image and VM size. The operator pins current and target images, rehearses startup and release commands, updates one stateless Machine, observes health and latency, then rolls forward. A separate volume move uses a verified snapshot and restore path.

Error Handling

FailureResponse
Provider contract changed during migrationPause, refresh documentation and client schemas, and reapprove the plan.
Canary is incompatible with attached storageUse rolling or a data-specific migration path; do not force the strategy.
Data reconciliation differsStop writes or rollout as planned, preserve both sides, and restore or reverse before the rollback window closes.

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/flyio-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Flyio Upgrade Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Flyio Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flyio Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Backend Test WorkerCorrectRoadH/OpenTickly307—~1.3kAutomated safety check: PassAGPL-3.0
Ef Core Migrationsjihadkhawaja/Egroo178—~673Automated safety check: PassApache-2.0
Diagnose Cloud SessionFreakStudioCN/mpy-hardware-extension154—~809Automated safety check: NotesCustom licence
Add Oliphaunt Extensionf0rr0/oliphaunt106—~1.8kAutomated safety check: PassMIT
DB AdminEliasOulkadi/shokunin114—~2kAutomated safety check: NotesMIT

Similar skills

  • Backend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

    307 GitHub stars~1.3k tokensUpdated 2 days ago
    DatabasesAuto-check passed
  • Ef Core Migrations

    jihadkhawaja/Egroo

    Handle EF Core schema changes in Egroo. An agent skill from jihadkhawaja/Egroo.

    178 GitHub stars~673 tokensUpdated 6 mo ago
    DatabasesAuto-check passed
  • Diagnose Cloud Session

    FreakStudioCN/mpy-hardware-extension

    用户报告 Blockless 扩展在云端实测时出问题(卡死/灰屏/跳步/构建失败),但本地复现不了、日志不在本地文件里时,用这个从云端托管数据库拉真实 session 定位症状与根因 / Use when a user reports an in-product Blockless bug from live cloud-backend testing and the real session…

    154 GitHub stars~809 tokensUpdated 13 days ago
    DatabasesAuto-check: notes
  • Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package…

    106 GitHub stars~1.8k tokensUpdated today
    DatabasesAuto-check passed
  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 6 days ago
    DatabasesAuto-check: notes
  • Postgresql Table Design

    ynulihao/AgentSkillOS

    Design a PostgreSQL-specific schema. An agent skill from ynulihao/AgentSkillOS.

    618 GitHub starsUsed in 15 repos~4k tokens
    DatabasesAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Flyio Upgrade Migration

What does Flyio Upgrade Migration do?

Migrate Fly.io app configuration, runtime images, Machine resources, regions, volumes, or Managed Postgres through staged change control. Flyio Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace.io app configuration, runtime images, Machine resources, regions, volumes, or Managed Postgres through staged change control.

When should I use Flyio Upgrade Migration?

Flyio Upgrade Migration fits situations like: upgrading a live workload; with: upgrade Fly app; migrate Fly region; change Fly runtime safely.

How do I install Flyio Upgrade Migration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill flyio-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/flyio-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/flyio-upgrade-migration in your project. Claude Code loads it when a task matches its description.

How do I install Flyio Upgrade Migration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill flyio-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/flyio-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/flyio-upgrade-migration in your project. Codex loads it when a task matches its description.

Can I use Flyio Upgrade Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill flyio-upgrade-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flyio-upgrade-migration, .gemini/skills/flyio-upgrade-migration, .github/skills/flyio-upgrade-migration and .opencode/skills/flyio-upgrade-migration in your project.

What does Flyio Upgrade Migration need to run?

SKILL.md names no scripts, command-line tools or credentials: Flyio Upgrade Migration is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires current and target contracts, an immutable backup or export where data is involved, a representative staging boundary, and approved rollback criteria..

Does Flyio Upgrade Migration access the network?

SKILL.md names 2 domains. As links in the text: fly.io and github.com. This is read from the text; nothing was executed.

Is Flyio Upgrade Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Flyio Upgrade Migration use?

Flyio Upgrade Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Flyio Upgrade Migration use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 506 tokens, read only when the agent opens those files.

What are the alternatives to Flyio Upgrade Migration?

Skills that share tags, products or a category with Flyio Upgrade Migration: Backend Test Worker (CorrectRoadH/OpenTickly, 307 stars), Ef Core Migrations (jihadkhawaja/Egroo, 178 stars), Diagnose Cloud Session (FreakStudioCN/mpy-hardware-extension, 154 stars) and Add Oliphaunt Extension (f0rr0/oliphaunt, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flyio Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.