central-station
This skill should be used when the user asks about Central Station threads, community discussions, support questions, feature requests, or wants to search Railway's community knowledge base. Use for queries like "search central station", "find threads about", "what are people asking about", "recent support threads", or "central station topics".
- Installs
- 1.5K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/railwayapp/railway-skills --skill central-station- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads central-station automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Central Station
Search and browse Railway's Central Station - the community support platform for threads, discussions, and documentation.
API Endpoints
| Endpoint | URL |
|---|---|
| GraphQL | https://station-server.railway.com/gql |
| Thread Markdown | https://station-server.railway.com/api/threads/:slug |
| LLM Data Export | https://station-server.railway.com/api/llms-station |
| Frontend | https://station.railway.com |
When to Use
- User wants to search Central Station threads or docs
- User asks about community discussions or support questions
- User wants to find threads about a specific topic (deployments, databases, etc.)
- User asks "what are people asking about X"
- User wants to see recent threads or questions
- User mentions Central Station, community threads, or support discussions
- User wants to find existing solutions before creating a new thread
When NOT to Use
- User wants Railway product documentation - use
railway-docsskill - User wants to check their project status - use
statusskill - User wants to manage their Railway project - use appropriate skill (deploy, environment, etc.)
Docs Search
For official Railway documentation, use the railway-docs skill which fetches from https://docs.railway.com/api/llms-docs.md.
Central Station's unifiedSearch can identify document types but has limited field access:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
--data-raw '{"query":"{ unifiedSearch(input: { query: \"volumes\", limit: 10 }) { results { document { __typename } } } }"}'
Document types returned: EsThreadItem (threads) and DocSearchResult (docs).
Note: For searching thread content, use the LLM Data Export endpoint instead (see below) which provides full thread data.
Quick Actions
Get Recent Threads
Fetch recent threads, optionally filtered by topic:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ threads(first: 10, sort: recent_activity) { edges { node { slug subject status topic { slug displayName } upvoteCount createdAt } } } }"}'
With topic filter:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ threads(first: 10, sort: recent_activity, topic: \"questions\") { edges { node { slug subject status topic { displayName } upvoteCount } } } }"}'
Get Thread by Slug
Fetch a specific thread with its content:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ thread(slug: \"THREAD_SLUG\") { slug subject status content { data } topic { displayName } upvoteCount } }"}'
Get Thread as Markdown
For a cleaner read, fetch the thread as markdown:
# Append .md to the frontend URL (requires topic slug)
curl -s 'https://station.railway.com/TOPIC_SLUG/THREAD_SLUG.md'
# Or use API with format query parameter
curl -s 'https://station-server.railway.com/api/threads/THREAD_SLUG?format=md'
# Or use API with Accept header
curl -s 'https://station-server.railway.com/api/threads/THREAD_SLUG' \
-H 'Accept: text/markdown'
List Topics
Get all available topics:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ topics { slug displayName displayNamePlural } }"}'
Returns: questions, feedback, community, billing, bug-bounty, privacy, abuse, templates
Get Trending Threads
Fetch currently trending threads:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ trendingThreads { slug subject status topic { displayName } upvoteCount } }"}'
Get Pinned Threads
Fetch pinned/important threads:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ pinnedThreads { slug subject topic { displayName } } }"}'
Search via LLM Data Export
For searching thread content, fetch all threads and filter locally:
curl -s 'https://station-server.railway.com/api/llms-station' | jq '.items[] | select(.title | test("postgres"; "i")) | {title, topic: .topic.name, status: .metadata.status}'
This endpoint returns all public threads with full content, useful for searching by keywords.
Thread Statuses
| Status | Description |
|---|---|
OPEN | Unresolved, accepting responses |
SOLVED | Marked as resolved |
AWAITING_RAILWAY_RESPONSE | Waiting for Railway team |
AWAITING_USER_RESPONSE | Waiting for original poster |
CLOSED | No longer accepting responses |
ARCHIVED | Old thread, preserved for reference |
Sort Options
For the threads query, use the sort parameter:
| Sort Value | Description |
|---|---|
recent_activity | Most recently active (default) |
newest | Newest first |
highest_votes | Most upvoted |
Presenting Results
When showing threads:
- Thread title - The subject
- Topic - Category (questions, feedback, etc.)
- Status - Open, solved, awaiting response
- Summary - Brief preview from content
- Link -
https://station.railway.com/{topic_slug}/{thread_slug}
Format example:
Found 3 threads about "postgres":
1. "Connection timeout when connecting to Postgres"
Topic: questions | Status: SOLVED | Upvotes: 5
https://station.railway.com/questions/connection-timeout-postgres
2. "How to connect to Postgres from local development"
Topic: community | Status: OPEN | Upvotes: 12
https://station.railway.com/community/connect-postgres-local
3. "Postgres SSL certificate verification failed"
Topic: questions | Status: AWAITING_RAILWAY_RESPONSE
https://station.railway.com/questions/postgres-ssl-verification
Common Search Patterns
| User Query | Filter/Search |
|---|---|
| "Why is my deploy failing?" | topic: questions, search: "deploy" |
| "Can't connect to database" | topic: questions, search: "database" or "postgres" |
| "Domain not working" | topic: questions, search: "domain" |
| "Feature requests" | topic: feedback |
| "What are people building?" | topic: community |
Composability
- After finding a thread: Summarize the solution or link to it
- No results found: Suggest using
railway-docsskill or creating a new thread - Technical issue found: Use relevant skill (deploy, environment, etc.) to help fix it
Error Handling
No Results Found
No threads found. Try:
- Different topic filter
- Checking Railway docs instead
- Creating a new thread at https://station.railway.com
Invalid Topic
List available topics first:
curl -s 'https://station-server.railway.com/gql' -H 'content-type: application/json' -d '{"query": "{ topics { slug } }"}'
Thread Not Found
Thread not found. It may have been deleted or marked private.
FAQ
What does the central-station skill do?
This skill should be used when the user asks about Central Station threads, community discussions, support questions, feature requests, or wants to search Railway's community knowledge base. Use for queries like "search central station", "find threads about", "what are people asking about", "recent support threads", or "central station topics".
How do I install central-station?
Run npx skills add https://github.com/railwayapp/railway-skills --skill central-station in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/central-station/ (personal) or .claude/skills/central-station/ (project).
Which AI agents can use central-station?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is central-station safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains central-station?
It is published by railwayapp in railwayapp/railway-skills. It has 1,509 recorded installs.
More from railwayapp/railway-skills
use-railway
railwayapp/railway-skills
Operate Railway infrastructure: sign up for or sign in to a Railway account, create projects, provision services, databases, and buckets, deploy code, configure infrastructure as code, environments and variables, manage domains, trace requests with OpenTelemetry, troubleshoot failures, check status and metrics, manage feature flags, database recovery and HA, cloud agents, usage limits, and Railway agent tooling. Use this skill whenever the user mentions Railway, feature flags, flag rollout, targeting rules, signing up, creating an account, registering, logging in, deployments, services, environments, buckets, object storage, tracing, traces, spans, OpenTelemetry, OTLP, build failures, agent setup, MCP, or infrastructure operations, even if they don't say "Railway" explicitly. Also invoke it when the user asks to be signed up, registered, or onboarded: do not refuse — drive them through the unauthed railway up flow (deploys + signs up on the fly) or railway login (which creates acco
service
railwayapp/railway-skills
This skill should be used when the user asks about service status, wants to rename a service, change service icons, link services, or create services with Docker images. For creating services with local code, prefer the new skill. For GitHub repo sources, use new skill to create empty service then environment skill to configure source.
status
railwayapp/railway-skills
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-docs
railwayapp/railway-skills
This skill should be used when the user asks about Railway features, how Railway works, or shares a docs.railway.com URL. Fetches up-to-date Railway docs to answer accurately.
deployment
railwayapp/railway-skills
This skill should be used when the user wants to manage Railway deployments, view logs, or debug issues. Covers deployment lifecycle (remove, stop, redeploy, restart), deployment visibility (list, status, history), and troubleshooting (logs, errors, failures, crashes, why deploy failed). NOT for deleting services - use environment skill with isDeleted for that.
deploy
railwayapp/railway-skills
This skill should be used when the user wants to push code to Railway, says "railway up", "deploy", "deploy to railway", "ship", or "push". For initial setup or creating services, use new skill. For Docker images, use environment skill.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.