Fly.io Connector for Muse
List apps and machines, manage machine lifecycle, run exec commands.
- What
- List apps and machines, manage machine lifecycle, run exec commands.
- Cost
- Free
- Needs
- A Fly.io API token (run `flyctl auth token` or create one in the Fly.io dashboard under Account > Tokens), kept in your Muse's secure vault (never paste secrets here). Note: creating machines incurs Fly.io usage costs (free allowances included); exec runs commands inside your machines — confirm each one.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that manages your Fly.io Machines through the Machines REST API: list apps and machines, inspect machines and volumes, create machines, stop/start/restart them, and run one-off commands inside a machine with exec. Reading needs no confirmation; machine create/stop/start/restart are writes — the skill confirms the exact action on the exact machine first, and exec is confirmation-gated with an explicit warning (never destructive without you seeing the exact command). Honest note: creating machines incurs Fly.io usage costs; Fly.io includes free allowances. Draft: written from Fly.io's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A Fly.io API token (run `flyctl auth token` or create one in the Fly.io dashboard under Account > Tokens), kept in your Muse's secure vault (never paste secrets here). Note: creating machines incurs Fly.io usage costs (free allowances included); exec runs commands inside your machines — confirm each one. No GitHub account needed unless listed here. Install "Fly.io Connector for Muse" for me. A Muse agent skill that manages Fly.io Machines: list apps and machines, manage volumes, start/stop/restart machines, run exec commands. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/flyio 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "flyio". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Fly.io API token in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.