Read and write Railway: list projects and deployments, set environment variables, redeploy. Trigger phrases: railway, deploy.
npx skills add https://github.com/Anil-matcha/awesome-muse-connectors --skill railway
Read and write the user's Railway infrastructure through the Railway GraphQL API: list projects, inspect a project, list deployments, set environment variables, and redeploy deployments. Use when the user mentions Railway or deployments they host there.
All commands go through bin/railway.py:
bin/railway.py auth # verify the token
bin/railway.py projects # list projects (id, name)
bin/railway.py project --id proj_abc123 # inspect one project
bin/railway.py deployments --project-id proj_abc123 # list deployments for a project
bin/railway.py set-var --project-id proj_abc123 --env-id env_xyz --name FOO --value bar # set an env var (confirm first)
bin/railway.py redeploy --deployment-id dep_abc123 # redeploy a deployment (confirm first)
Every operation is a POST to the single GraphQL endpoint with {"query": ..., "variables": {...}}. Queries are kept minimal; project and deployments accept the IDs Railway returns from projects.
railway (credential is collected as custom.railway)credentials.request_api_access); created in the Railway dashboard under Tokens. Note: project tokens are a different mechanism (they use a Project-Access-Token header instead of Authorization: Bearer) and are out of scope for this CLI.backboard.railway.combin/railway.py auth (must return "ok": true)set-var and redeploy are writes: confirm the project, environment, variable name, and value with the user before running, unless standing permission exists..get.🧪 Draft: written from Railway's public API docs; not yet live-tested end-to-end.
Take anil-matcha/railway from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.