New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Flyio Core Workflow A

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

Operate a Fly.io application release from configuration review through deploy, scale, secret change, and rollback.

MITAuto-check passedDevOps & Cloud

Install Flyio Core Workflow A

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

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace flyio-core-workflow-a --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-core-workflow-a .claude/skills/flyio-core-workflow-a && 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-core-workflow-a
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
519 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Operate a Fly.io application release from configuration review through deploy, scale, secret change, and rollback.

  • Works in 6 steps: Inventory the current app → Render the desired state → Stage secrets separately → …
  • Changing a Fly Launch app
  • 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 Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace. Operate a Fly.io application release from configuration review through deploy, scale, secret change, and rollback. Use when shipping or changing a Fly Launch app. Trigger with: "deploy Fly app", "scale Fly Machines", "roll back Fly release".

Its SKILL.md is about 1.2k 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 an existing Fly.io organization, an approved app target, a deploy-capable scoped identity, and a tested health and rollback contract.

It sits in DevOps & Cloud, covering Deployment. 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

  • Changing a Fly Launch app
  • With: deploy Fly app
  • Scale Fly Machines
  • Roll back Fly release

Example prompts

  • “deploy Fly app”
  • “scale Fly Machines”
  • “roll back Fly release”
  • “/flyio-core-workflow-a”

Requirements

  • Compatibility (from SKILL.md): Requires an existing Fly.io organization, an approved app target, a deploy-capable scoped identity, and a tested health and rollback contract.
  • Pre-approved tools (allowed-tools): Read, Grep, Write, Edit

Workflow steps

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

  1. Inventory the current app
  2. Render the desired state
  3. Stage secrets separately
  4. Select the deployment strategy
  5. Deploy and wait
  6. Reconcile or roll back

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

    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 an existing Fly.io organization, an approved app target, a deploy-capable scoped identity, and a tested health and rollback contract.

    From compatibility in the SKILL.md frontmatter.

Context cost

Flyio Core Workflow A loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 519 words of instructions outside code blocks.

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

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). 519 words, ~1,212 tokens.

Download SKILL.mdSave it as .claude/skills/flyio-core-workflow-a/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
flyio-core-workflow-a
description
Operate a Fly.io application release from configuration review through deploy, scale, secret change, and rollback. Use when shipping or changing a Fly Launch app. Trigger with: "deploy Fly app", "scale Fly Machines", "roll back Fly release".
allowed-tools
Read, Grep, Write, Edit
compatibility
Requires an existing Fly.io organization, an approved app target, a deploy-capable scoped identity, and a tested health and rollback contract.
version
2.0.0
argument-hint
[app-environment-and-release]
model
inherit
effort
high
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, flyio, deployments, scaling, secrets

Fly.io Application Release Lifecycle

Overview

Treat the app release as a state transition with explicit configuration, image, capacity, health, and rollback boundaries. Fly Launch manages Machines from fly.toml, but production success still requires reconciliation against the running fleet.

Prerequisites

  • Source revision, image build contract, app name, environment, and primary region
  • Reviewed fly.toml with process groups, services, health checks, and shutdown settings
  • Approved deploy strategy, capacity envelope, secret plan, and rollback target

Instructions

Step 1: Inventory the current app

Record current release, running image, Machine counts and regions, health, IP allocation, secrets digests, and attached storage.

Step 2: Render the desired state

Review build, process groups, services, concurrency, autostart or autostop, VM resources, regions, mounts, release command, and deployment policy.

Step 3: Stage secrets separately

Use Fly secrets rather than plaintext [env] values. Decide whether a secret change should restart Machines immediately or be staged for the release.

Step 4: Select the deployment strategy

Use rolling by default. Use canary only when temporary extra capacity is valid and no Machine volume blocks it; use blue-green only with health checks and compatible stateless capacity.

Step 5: Deploy and wait

Bind the release to an immutable image, observe replacement, and wait for health and Machine convergence. Do not infer success from image push alone.

Step 6: Reconcile or roll back

Compare desired and actual image, count, regions, health, and service behavior. Roll back if acceptance criteria or error budgets fail.

Authentication

Use an app-scoped deploy token for a single app and a short-lived organization token only when the operation legitimately spans apps. Fly App secrets are encrypted at rest but become environment variables inside Machines; anyone with deploy access can deploy code that reads them.

Show full SKILL.md (237 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

  • Preflight snapshot and desired-state review
  • Release plan with strategy, capacity, health, and rollback gates
  • Post-release reconciliation receipt or rollback record

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

A stateless API with two healthy Machines uses a rolling release. The operator stages one secret, pins the image digest, deploys one Machine at a time, verifies the health endpoint and image on both Machines, and closes only after the previous image remains available for rollback.

Error Handling

FailureResponse
Release command failsStop the release, retain its logs, and fix the migration or command contract before retrying.
Replacement cannot become healthyPreserve the failed Machine evidence and roll back rather than widening unavailable capacity.
Desired and actual fleet differRe-read current state, identify an interrupted or concurrent change, and reconcile under one release owner.

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-core-workflow-a of jeremylongshore/tons-of-skills-marketplace.

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

Open the folder on GitHubat commit cfae287

Compare with similar skills

Flyio Core Workflow A 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 Core Workflow A compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flyio Core Workflow A this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Mirrord Operatormetalbear-co/mirrord5.4k1 repos~4.6kAutomated safety check: PassMIT
KubeSphere ServiceMesh Managerkubesphere/kubesphere17k—~2.4kAutomated safety check: PassCustom licence
Vercelremotion-dev/remotion63k—~1.2kAutomated safety check: PassCustom licence

Similar skills

  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Mirrord Operator

    metalbear-co/mirrord

    Help users install and configure the mirrord Operator for team/enterprise environments.

    5.4k GitHub starsUsed in 1 repo~4.6k tokens
    DevOps & CloudAuto-check passed

  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Vercel

    remotion-dev/remotion

    Official

    Set up a Codex monitor for Vercel deployments and preview URLs.

    63k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-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

Categories

Questions about Flyio Core Workflow A

What does Flyio Core Workflow A do?

Operate a Fly.io application release from configuration review through deploy, scale, secret change, and rollback. Flyio Core Workflow A is an agent skill from jeremylongshore/tons-of-skills-marketplace.io application release from configuration review through deploy, scale, secret change, and rollback.

When should I use Flyio Core Workflow A?

Flyio Core Workflow A fits situations like: changing a Fly Launch app; with: deploy Fly app; scale Fly Machines; roll back Fly release.

How do I install Flyio Core Workflow A in Claude Code?

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

How do I install Flyio Core Workflow A in Codex?

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

Can I use Flyio Core Workflow A 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-core-workflow-a -a cursor` (or -a -a, -a or -a for the others). To copy it by hand, put the folder in .cursor/skills/flyio-core-workflow-a, .gemini/skills/flyio-core-workflow-a, .github/skills/flyio-core-workflow-a and .opencode/skills/flyio-core-workflow-a in your project.

What does Flyio Core Workflow A need to run?

SKILL.md names no scripts, command-line tools or credentials: Flyio Core Workflow A is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Write, Edit. Compatibility (from SKILL.md): Requires an existing Fly.io organization, an approved app target, a deploy-capable scoped identity, and a tested health and rollback contract..

Does Flyio Core Workflow A access the network?

SKILL.md names 1 domain. As links in the text: fly.io. This is read from the text; nothing was executed.

Is Flyio Core Workflow A 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 Core Workflow A use?

Flyio Core Workflow A 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 Core Workflow A use?

About 1.2k tokens (SKILL.md is roughly 4.8k 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 471 tokens, read only when the agent opens those files.

What are the alternatives to Flyio Core Workflow A?

Skills that share tags, products or a category with Flyio Core Workflow A: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Mirrord Operator (metalbear-co/mirrord, 5.4k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flyio Core Workflow A?

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.