projects

List, switch, and configure Railway projects via GraphQL mutations.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/sethdavis512/iridium-tambo --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-tambo/tree/main/.agents/skills/projects
Command: npx skills add https://github.com/sethdavis512/iridium-tambo --skill projects-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Managing multiple Railway projects, workspaces, and settings can be tedious and error-prone. This skill centralizes listing, switching, and configuring projects to streamline governance and reduce mistakes.

Core Features & Use Cases

  • List Projects: quickly enumerate projects and workspaces with essential fields
  • Switch Projects: change the current project context for subsequent commands
  • Update Project Settings: modify visibility, PR deploys, and other project options via Railway API mutations
  • Use Case: switch to a different project to deploy a PR or adjust accessibility for a team

Quick Start

Ask to list my Railway projects and switch to the target project by name.

Frequently Asked Questions about projects

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

FAQPage Schema
How do I list and switch Railway projects from the command line?

To list and switch Railway projects, you can use an automation script that calls the Railway API via GraphQL to fetch project catalogs and change your current workspace context. This simplifies managing multiple projects.

How can I update Railway project settings like visibility and PR deploys?

You can update Railway project settings by executing GraphQL mutations through the Railway API to modify visibility, enable PR deploys, and adjust other project options. This automates configuration changes across your workspaces.

Do I need jq and a Railway token to manage projects with API scripts?

Yes, managing Railway projects with API scripts requires a valid Railway token for authentication and jq for processing the JSON responses from GraphQL queries and mutations. These dependencies are necessary for the script to function.

What is the best way to manage multiple Railway workspaces without errors?

The best way to manage multiple Railway workspaces is by centralizing project context switching and configuration updates through an API script. This reduces manual errors and streamlines governance across different environments.

Can I change the current Railway project context for subsequent deployment commands?

Yes, you can change the current Railway project context for subsequent deployment commands by switching the active project using the API script. This ensures your following operations target the correct workspace and project.