use-railway

The use-railway skill provides a comprehensive interface for managing cloud infrastructure on the Railway platform. Designed for engineers and developers, this tool automates the lifecycle of cloud resources, from initial service provisioning to production troubleshooting and performance analysis. It acts as a bridge between the agent and the Railway CLI, allowing for precise context-aware operations across workspaces, projects, environments, and services.

• Infrastructure Lifecycle: Create and configure projects, deploy code from repositories or Docker images, and manage isolated configuration environments such as production, staging, or development.

• Database & Storage Management: Provision and inspect managed databases including PostgreSQL, MySQL, Redis, and MongoDB, and manage S3-compatible object storage buckets for persistent file assets.

• Observability & Troubleshooting: Retrieve deployment logs, monitor build status, and fetch runtime metrics. It includes specialized analysis scripts to inspect database health, latency, connection pooling, and resource utilization.

• Configuration & Networking: Manage environment variables, secrets, domain configurations, and network settings directly through the CLI or API.

• Intelligent Routing: Automatically identifies user intent based on queries related to deployments, infrastructure failures, or service status, and routes requests to the appropriate specialized reference material.

• The skill requires the Railway CLI installed and appropriate authentication via railway login. Usage is most effective when providing specific Railway dashboard URLs, which the agent will parse to extract project, service, and environment IDs.

• Prefer using explicit IDs passed via flags like --project, --service, and --environment to maintain predictable state without modifying global configuration.

• For complex database issues, the skill provides specific analysis routines (analyze-db) that prioritize deep metrics collection over standard status checks.

• Supports JSON output for automated scripting and reliable parsing of complex resource metadata.

• Constrained by Railway's resource hierarchy; always verify the current working context using railway status --json before performing destructive mutations or configuration patches.