Agent skill · software engineering · davila7
railway-environment
Query, stage, and apply configuration changes for Railway environments. Use for ANY variable or env var operations, service configuration (source, build settings, deploy settings), lifecycle (delete service), and applying changes. Prefer over railway-status skill for any configuration or variable queries.
Why this skill is useful
Adds specific commands and workflows for managing Railway environments that the AI wouldn't reliably generate on its own.
What it needs
Requires railway-cli installed locally. About 5k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Environment Configuration Query, stage, and apply configuration changes for Railway environments. Shell Escaping CRITICAL: When running GraphQL queries via bash, you MUST wrap in heredoc to prevent shell escaping issues: Without the heredoc wrapper, multi-line commands break and exclamation marks in GraphQL non-null types get escaped, causing query failures. When to Use User wants to create a new environment User wants to duplicate an environment (e.g., "copy production to staging") User wants to switch to a different environment User asks about current build/deploy settings, variables, replicas, health checks, domains User asks to change service source (Docker image, branch, commit, root directory) User wants to connect a service to a GitHub repo User wants to deploy from a GitHub repo (create empty service first via railway-new skill, then use this) User asks to change build or start command User wants to add/update/delete environment variables User wants to change replica count or configure health checks User asks to delete a service, volume, or bucket User says "apply changes", "commit changes", "deploy changes" Auto-fixing build errors detected in logs Create Environment Create a new environment in the linked project: Duplicate an existing environment: With service-specific variables: Switch Environment Link a different environment to the current directory: Or by ID: Get Context Extract: project.id - for service lookup environment.id - for the mutations service.id - default service if user doesn't specify one Resolve Service ID If user specifies a service by name, query project services: Match the service name (case-insensitive) to get the service ID. Query Configuration Fetch current environment configuration and staged changes. Example: Response Structure The config field contains current configuration: The patch field in environmentStagedChanges contains pending changes. The effective configuration is the base config merged with the staged patch. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/environment