railwayapp/railway-skills▌

Complete Railway infrastructure management: projects, services, databases, deployments, environments, object storage, and troubleshooting. \n \n Operates across Railway's resource hierarchy: workspaces, projects, environments, services, buckets, and deployments with CLI context management \n Covers five operational domains: resource setup, code deployment, configuration management, health monitoring, and API/docs access \n Includes preflight authentication checks, context resolution, and multi-s

Fetch current Railway documentation to answer platform questions accurately. \n \n Provides LLM-optimized sources including full docs, templates, changelog, and blog posts accessible via .md file extensions \n Covers core Railway topics: projects, deployments, volumes, variables, CLI, and pricing \n Designed to be called before answering Railway questions from memory, ensuring responses reflect the latest documentation \n Supports direct doc.railway.com URL conversion by appending .md for markdo

Search and deploy pre-configured services from Railway's template marketplace. \n \n Supports 20+ templates across databases (PostgreSQL, Redis, MySQL, MongoDB), CMS platforms (Ghost, Strapi), storage (Minio), automation (n8n), and monitoring (Uptime Kuma) \n Query templates by category or verification status; fetch template details including serialized configuration needed for deployment \n Deploy templates to a project and environment in two steps: fetch template metadata, then execute deploym

Query CPU, memory, network, and disk usage metrics for Railway services. \n \n Supports nine metric types including CPU usage, memory, network traffic (RX/TX), and disk usage across deployments and instances \n Query metrics for a single service or all services in an environment using optional groupBy parameters (by deployment, instance, region, or service) \n Requires environmentId from railway status --json ; serviceId is optional to retrieve metrics across all services \n Time-based queries w

Generate Railway domains or add custom domains to services with DNS configuration. \n \n Supports two domain types: auto-generated Railway domains (one per service) and custom domains with DNS record configuration \n CLI commands for adding domains, viewing current domains via the environment skill, and removing domains through environment configuration \n Requires an active service deployment; integrates with the environment and service skills for reading and modifying domain settings \n Return

Initialize Railway projects, add services, and configure deployments with automatic project detection. \n \n Handles three workflows: creating new projects with railway init , linking existing projects with railway link , and adding services to linked projects with railway add --service \n Automatically detects project state via railway status --json and walks up directory trees to find parent project links, avoiding unnecessary re-initialization \n Supports scaffolding for static sites (Vite, A

Read and edit Railway environment configuration, variables, build settings, and service deployment parameters. \n \n Fetch current environment config including source, build/deploy settings, variables, and networking via railway environment config --json \n Create new environments, duplicate existing ones with optional service-specific variable overrides, or switch between environments \n Edit configuration atomically using JSON patches: set build/start commands, add/update/delete variables, cha

List, switch, and configure Railway projects with CLI commands and GraphQL mutations. \n \n List all projects and workspaces, or switch between projects using railway link and project IDs \n Rename projects, enable/disable PR deploys, toggle public/private visibility, and configure bot PR environments via GraphQL mutations \n Extract project IDs from railway status --json to use in update operations \n Composable with status , new , and environment skills for viewing details, creating projects,

Deploy PostgreSQL, Redis, MySQL, or MongoDB with pre-configured volumes, networking, and connection variables. \n \n Supports four official database templates: PostgreSQL, Redis, MySQL, and MongoDB, each with persistent volumes and automatic connection variable setup \n Always checks for existing databases before creating to avoid duplicates; queries environment config via GraphQL to detect running instances \n Provides reference variables for connecting other services (e.g., ${{Postgres.DATABAS

Push code to Railway with railway up , supporting detach and CI streaming modes. \n \n Two deployment modes: detach (default, returns immediately) and CI (streams build logs until complete) \n Always include a -m flag with a descriptive commit message summarizing the changes being deployed \n Supports targeting specific services and environments via --service and --environment flags, or deploying to unlinked projects with --project and --environment \n CLI automatically walks up the directory tr

View, manage, and troubleshoot Railway deployments with logs, redeploy, and removal commands. \n \n List deployments and view deploy or build logs with filtering by level, text search, time range, or specific deployment ID \n Redeploy the most recent deployment or restart containers without rebuilding to pick up external resource changes \n Remove deployments (stops the service but keeps it intact; use the environment skill to delete services entirely) \n Supports JSON output for all commands an

Search and browse Railway's community support platform for threads, discussions, and solutions. \n \n Query recent, trending, or pinned threads across eight topics (questions, feedback, community, billing, bug-bounty, privacy, abuse, templates) with filtering by status and sort order \n Search thread content via GraphQL unified search or LLM data export endpoint for full-text keyword matching across all public threads \n Fetch individual threads as structured data or rendered markdown for clean

Check current Railway project status, services, and deployment state. \n \n Verifies Railway CLI installation and authentication before querying project status \n Returns project name, workspace, active environment, and list of services with their deployment status \n Displays active deployments and configured domains for the linked project \n Handles common errors: missing CLI, authentication failures, and unlinked projects with clear remediation steps \n

Create, rename, and manage services; check deployment status and health. \n \n Check service status, deployment history, and health via CLI commands returning JSON \n Create services with Docker images or empty (GitHub repos configured via environment skill) \n Rename services and update icons using GraphQL mutations; supports image URLs, animated GIFs, and Railway Devicons \n Link or switch between services in the current directory with railway service link \n