use-railway

Drive the installed railway CLI from evidence, not memory. This skill is the routing layer: it picks the right reference, the right command, and the right scope (local binary vs upstream docs) for every Railway question an agent runs into during ongoing platform operations.

Use this skill when

• the user types or pastes a literal railway <subcommand> and wants the right flags, aliases, or nested forms
• the job is choosing between near-twin commands — up vs deploy, redeploy vs restart, delete vs unlink, connect vs ssh, run vs shell vs dev
• the user is reading logs, checking deploy status, scaling a service, editing variables, attaching a domain, or opening a DB shell against a Railway service
• the user pastes a Railway dashboard URL or asks "which project/service/environment am I linked to?"
• the docs show a Railway command the local binary does not have, or the user says "latest", "current", "today" — version-drift reconciliation
• the question is about Railway functions, volumes, or shell completion output for the installed CLI
• the user wants first-party Railway database analysis (Postgres, MySQL, Redis, Mongo) rooted in CLI access

Do NOT use this skill when

• the job is authoring a make prod / make deploy target or a Makefile control plane that wraps Railway commands — use init-makefiles to generate the scenario-appropriate scaffold; this skill answers what the wrapped commands do, but does not write the Makefile
• the work is purely Railway dashboard, GraphQL API, or REST API with no CLI decision to make
• a generic shell, Git, or container-build skill answers the question with no Railway-specific context