ericrisco/rsc-harness / skills/fly-io
fly-io
VerifiedUse when deploying or operating an app on Fly.io — writing fly.toml, placing Machines in regions near users, attaching Volumes, managing secrets, or picking a scaling lever (autostop/autostart, scale count, fly-replay). NOT choosing which host to deploy on (that is `deployment`), NOT a git-push PaaS with no regions model (that is `railway`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| evals/README.md | markdown | 710 B |
| evals/cases.yaml | config | 2.6 KB |
| references/fly-toml.md | markdown | 4.7 KB |
| references/multi-region.md | markdown | 3.5 KB |
| scripts/verify.shexecutable | script | 2.6 KB |
evals/README.md
View on GitHub# Evals for fly-io
These cases are routing/trigger fixtures, not executed tests. To run them, read each `should_trigger` prompt against this skill's `description` and body and confirm it would load fly-io (the non-obvious ones — the `iad`/latency prompt with no "Fly" keyword, and the Catalan one — are the real checks). Read each `should_not_trigger` prompt and confirm it routes to the named sibling (`railway`, `vercel`, `docker`, `scaling`) instead. For the `capability` case, draft the fly.toml + commands the scenario asks for and check it against every `must_include` rubric line. There is no test runner; the rigor is whether a fresh agent reaches the same trigger, routing, and rubric decisions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |