central-station

Search and browse Railway's community support platform for threads, discussions, and solutions.

railwayapp/railway-skillsUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

225

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/railwayapp/railway-skills --skill central-station

0

installs

0

this week

225

stars

What it does

  • Query recent, trending, or pinned threads across eight topics (questions, feedback, community, billing, bug-bounty, privacy, abuse, templates) with filtering by status and sort order

  • Search thread content via GraphQL unified search or LLM data export endpoint for full-text keyword matching across all public threads

  • Fetch individual threads as structured data or rendered markdown for clean

Category

Productivity

Last updated

Apr 8, 2026

Installation Guide

How to use central-station on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add central-station
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/railwayapp/railway-skills --skill central-station

Fetches central-station from railwayapp/railway-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/central-station

Restart Cursor to activate central-station. Access via /central-station in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

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-docs skill
  • User wants to check their project status - use status skill
  • 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:

  1. Thread title - The subject
  2. Topic - Category (questions, feedback, etc.)
  3. Status - Open, solved, awaiting response
  4. Summary - Brief preview from content
  5. 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-docs skill 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.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.654 reviews
  • A
    Aisha KapoorDec 24, 2024

    central-station has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • A
    Aisha SinghDec 20, 2024

    I recommend central-station for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • K
    Kofi DialloDec 20, 2024

    Keeps context tight: central-station is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Y
    Yuki BhatiaDec 4, 2024

    central-station reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Z
    Zaid AbebeNov 23, 2024

    central-station is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • A
    Aditi KimNov 19, 2024

    central-station fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • H
    Henry DesaiNov 15, 2024

    Useful defaults in central-station — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • E
    Evelyn PerezNov 11, 2024

    Solid pick for teams standardizing on skills: central-station is focused, and the summary matches what you get after install.

  • K
    Kofi HuangNov 11, 2024

    Registry listing for central-station matched our evaluation — installs cleanly and behaves as described in the markdown.

  • S
    Shikha MishraOct 18, 2024

    central-station reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 54

1 / 6

Discussion

Comments — not star reviews
  • No comments yet — start the thread.