How do I install the Status skill?

Run npx skillmds@latest add artivilla/status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Status safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Status?

artivilla (@artivilla) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Status by artivilla — Agent Skill

Name: Status
Rating: 4.2 (5 reviews)
Author: artivilla

Status

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.

artivilla Updated Sep 9, 2026

File contents

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:

railway status --json

First verify CLI is installed:

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.).

---name: statusdescription: 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.--- # 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.).

Frequently asked questions