projects

List, switch, and configure Railway projects via CLI and GraphQL API.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill projects-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: projects
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/projects
Command: npx skills add https://github.com/sethdavis512/iridium --skill projects-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve? Managing Railway projects from the command line requires knowing the right CLI commands and GraphQL mutations, and raw JSON output from the Railway CLI is often too large to work with directly. This Skill provides the exact commands and API patterns to list, switch, rename, and configure projects without digging through documentation. ## Core Features & Use Cases - Project Discovery: List all projects and workspaces with condensed output, extracting only essential fields like project ID, name, and workspace. - Project Switching: Link a different project to the current directory using railway link by ID, name, or interactive selection. - Settings Management: Update project settings through the Railway GraphQL API, including renaming, toggling PR deploys, changing public/private visibility, and enabling bot PR environments. - Use Case: A developer wants to enable PR deploys and rename their staging project. The Skill retrieves the project ID via railway status --json, then runs the projectUpdate mutation through the included railway-api.sh helper script. ## Quick Start Ask the assistant to list all your Railway projects and workspaces, or to rename a specific project and enable PR deploys on it.

Frequently Asked Questions about projects

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all my Railway projects from the CLI?▼

Run `railway list --json` to get all projects, but the output can be very large. Extract only essential fields like project id, name, and workspace name rather than reading the full JSON response.

How do I switch to a different Railway project?▼

Use `railway link -p <project-id-or-name>` to link a different project to the current directory, or run `railway link` without arguments for interactive selection. Afterwards, run `railway status` to confirm the active project.

How do I rename a Railway project or enable PR deploys?▼

Get the project ID from `railway status --json`, then call the `projectUpdate` GraphQL mutation with a ProjectUpdateInput containing fields like name, prDeploys, isPublic, or botPrEnvironments via the Railway API.

How do I see which Railway workspaces I belong to?▼

Run `railway whoami --json` to return your user info along with all workspaces you belong to. This is useful before switching projects across different workspaces.

Why does the Railway API script fail with an authentication error?▼

The helper script reads your token from ~/.railway/config.json, which only exists after running `railway login`. If the config file is missing or the token is null, log in first and ensure jq is installed.

Can I update multiple Railway project settings in one request?▼

Yes, the ProjectUpdateInput accepts multiple fields in a single mutation. For example, pass {"name": "new-name", "prDeploys": true} together in the input object to rename and enable PR deploys simultaneously.