skills/railway/railway-central-station/SKILL.md
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".
npx skillsauth add The-Utopia-Studio/skills central-stationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Search and browse Railway's Central Station - the community support platform for threads, discussions, and documentation.
| 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 |
railway-docs skillstatus skillFor 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.
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 } } } }"}'
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 } }"}'
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'
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
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 } }"}'
Fetch pinned/important threads:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ pinnedThreads { slug subject topic { displayName } } }"}'
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.
| 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 |
For the threads query, use the sort parameter:
| Sort Value | Description |
|------------|-------------|
| recent_activity | Most recently active (default) |
| newest | Newest first |
| highest_votes | Most upvoted |
When showing threads:
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
| 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 |
railway-docs skill or creating a new threadNo threads found. Try:
- Different topic filter
- Checking Railway docs instead
- Creating a new thread at https://station.railway.com
List available topics first:
curl -s 'https://station-server.railway.com/gql' -H 'content-type: application/json' -d '{"query": "{ topics { slug } }"}'
Thread not found. It may have been deleted or marked private.
data-ai
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
development
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
development
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
development
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.