ericrisco/rsc-harness / skills/railway
railway
FlaggedUse when deploying an app to Railway — pushing a repo or running railway up, provisioning a managed database, wiring env and reference variables across services, attaching a volume, or fixing a deploy that builds but will not serve. NOT Render (that is `render`), NOT Fly machines (that is `fly-io`), NOT a self-hosted PaaS on your own box (that is `coolify`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.7 KB |
| evals/README.md | markdown | 1014 B |
| evals/cases.yaml | config | 3.5 KB |
| references/cli-cookbook.md | markdown | 4.5 KB |
| references/config-as-code.md | markdown | 4.3 KB |
| scripts/verify.shexecutable | script | 6.2 KB |
evals/README.md
View on GitHub# Evals — railway
`cases.yaml` holds three buckets. `should_trigger` lists prompts (with a `why`) where an agent
should reach for this skill, including non-obvious symptom phrasings (a 502 that never says
"bind") and Spanish phrasings. `should_not_trigger` lists nearby prompts that must route to a
real sibling (`render`, `fly-io`, `db-migrations`, `domains-dns`, `coolify`) with the routing
reason. `capability` is an end-to-end scenario with a `must_include` rubric.
There is no automated runner here. Evaluate by judgment or with your harness: feed each
`should_trigger` / `should_not_trigger` prompt to a router and check the selection matches; for
`capability`, have the agent produce a plan and check every `must_include` bullet is satisfied
(uses the real CLI flow, references `${{Postgres.DATABASE_URL}}`, binds `0.0.0.0:$PORT`, sets
`healthcheckPath`, and invents no fake commands). To sanity-check the emitted config artifact,
run `bash ../scripts/verify.sh` from a dir containing a `railway.json`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |