Service

Handles the lifecycle of Railway services: spin them up, tear them down, rename them, check if they're healthy or crashing. You'll reach for this when you need to provision a new service in a project, rename an existing one, or quickly check deployment status and health metrics. It's the bread and butter layer of Railway operations, one level below full infrastructure orchestration. Works best when you already know which service you want to touch. If you're debugging why something broke or need to trace through logs and metrics across multiple deployments, you'll want the broader infrastructure skill instead. This is for the straightforward service CRUD operations.