This skill should be used when the user asks "railway status", "is it running", "what's deployed", "deployment status", or about uptime. NOT for variables ("what variables", "env vars", "add variable") or configuration queries - use environment skill for those.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add The-Utopia-Studio/skills --skill railway-status --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Railway Status?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/the-utopia-studio-railway-status-skills)More formats (shields.io, HTML) on the badges page.
---
name: status
description: This skill should be used when the user asks "railway status", "is it running", "what's deployed", "deployment status", or about uptime. NOT for variables ("what variables", "env vars", "add variable") or configuration queries - use environment skill for those.
allowed-tools: Bash(railway:*), Bash(which:*), Bash(command:*)
---
# Railway Status
Check the current Railway project status for this directory.
## When to Use
- User asks about Railway status, project, services, or deployments
- User mentions deploying or pushing to Railway
- Before any Railway operation (deploy, update service, add variables)
- User asks about environments or domains
## When NOT to Use
Use the `environment` skill instead when user wants:
- Detailed service configuration (builder type, dockerfile path, build command, root directory)
- Deploy config (start command, restart policy, healthchecks, predeploy command)
- Service source (repo, branch, image)
- Compare service configs
- Query or change environment variables
## Check Status
Run:
```bash
railway status --json
```
First verify CLI is installed:
```bash
command -v railway
```
## Handling Errors
### CLI Not Installed
If `command -v railway` fails:
> Railway CLI is not installed. Install with:
> ```
> npm install -g @railway/cli
> ```
> or
> ```
> brew install railway
> ```
> Then authenticate: `railway login`
### Not Authenticated
If `railway whoami` fails:
> Not logged in to Railway. Run:
> ```
> railway login
> ```
### No Project Linked
If status returns "No linked project":
> No Railway project linked to this directory.
>
> To link an existing project: `railway link`
> To create a new project: `railway init`
## Presenting Status
Parse the JSON and present:
- **Project**: name and workspace
- **Environment**: current environment (production, staging, etc.)
- **Services**: list with deployment status
- **Active Deployments**: any in-progress deployments (from `activeDeployments` field)
- **Domains**: any configured domains
Example output format:
```
Project: my-app (workspace: my-team)
Environment: production
Services:
- web: deployed (https://my-app.up.railway.app)
- api: deploying (build in progress)
- postgres: running
```
The `activeDeployments` array on each service shows currently running deployments
with their status (building, deploying, etc.).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!