status_skill

This skill checks Railway project status and presents environments, services, and deployments to help you monitor uptime and progress.
  • Shell
  • Official

79

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill railwayapp/railway-skills --skill status

  • SKILL.md2.3 KB

Overview

This skill checks the current Railway project and deployment status for the directory you are in. It is designed to run the Railway CLI status command, interpret the JSON output, and present a concise, human-friendly summary of project, environment, services, active deployments, and domains. Use this skill when the user asks about deployment state, uptime, or what is currently deployed.

How this skill works

The skill verifies the Railway CLI is available and the user is authenticated, then runs railway status --json to retrieve structured project data. It parses the JSON to extract project name and workspace, current environment, service list with deployment statuses, any activeDeployments per service, and configured domains. If the CLI is missing, the user is unauthenticated, or no project is linked, the skill returns clear, actionable instructions to resolve the issue.

When to use it

  • User asks 'railway status', 'is it running', or 'what's deployed' for the current project
  • Before performing a deploy, update, or rollback to confirm current state
  • When the user wants a quick summary of services and any in-progress deployments
  • When checking which environment (production/staging) is currently active
  • When verifying domain configuration or service URLs

Best practices

  • Run this from the project directory that should be linked to a Railway project
  • Ensure Railway CLI is installed and you are logged in (railway login) before running status
  • If status reports 'No linked project', link with railway link or create one with railway init
  • Use the JSON output to programmatically inspect activeDeployments for build/deploy progress
  • Present concise summaries: project, environment, service list with status, active deployments, and domains

Example use cases

  • User asks 'Is my site up?' — report service statuses and public URLs
  • User asks 'What's deployed to production?' — show services in production and their deployment states
  • User asks 'Are there any deployments running?' — list activeDeployments and their progress
  • Pre-deploy checklist — verify no in-progress deployments and confirm environment
  • Troubleshooting — detect missing CLI, not logged in, or no linked project and provide fixes

FAQ

Install with npm install -g @railway/cli or brew install railway, then run railway login.

What if status says 'No linked project'?

Link an existing project with railway link or create one with railway init in the current directory.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational