deploy▌
railwayapp/railway-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Push code to Railway with railway up , supporting detach and CI streaming modes.
- ›Two deployment modes: detach (default, returns immediately) and CI (streams build logs until complete)
- ›Always include a -m flag with a descriptive commit message summarizing the changes being deployed
- ›Supports targeting specific services and environments via --service and --environment flags, or deploying to unlinked projects with --project and --environment
- ›CLI automatically walks up the directory tr
Deploy
Deploy code from the current directory to Railway using railway up.
When to Use
- User asks to "deploy", "ship", "push code"
- User says "railway up" or "deploy to Railway"
- User wants to deploy local code changes
- User says "deploy and fix any issues" (use --ci mode)
Commit Message
Always use the -m flag with a descriptive commit message summarizing what's being deployed:
railway up --detach -m "Add user authentication endpoint"
Good commit messages:
- Describe what changed: "Fix memory leak in worker process"
- Reference tickets/issues: "Implement feature #123"
- Be concise but meaningful: "Update deps and fix build warnings"
Modes
Detach Mode (default)
Starts deploy and returns immediately. Use for most deploys.
railway up --detach -m "Deploy description here"
CI Mode
Streams build logs until complete. Use when user wants to watch the build or needs to debug issues.
railway up --ci -m "Deploy description here"
When to use CI mode:
- User says "deploy and watch", "deploy and fix issues"
- User is debugging build failures
- User wants to see build output
Deploy Specific Service
Default is linked service. To deploy to a different service:
railway up --detach --service backend -m "Deploy description here"
Deploy to Unlinked Project
Deploy to a project without linking first:
railway up --project <project-id> --environment production --detach -m "Deploy description here"
Requires both --project and --environment flags.
CLI Options
| Flag | Description |
|---|---|
-m, --message <MSG> |
Commit message describing the deploy (always use this) |
-d, --detach |
Don't attach to logs (default) |
-c, --ci |
Stream build logs, exit when done |
-s, --service <NAME> |
Target service (defaults to linked) |
-e, --environment <NAME> |
Target environment (defaults to linked) |
-p, --project <ID> |
Target project (requires --environment) |
[PATH] |
Path to deploy (defaults to current directory) |
Directory Linking
Railway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked project, you don't need to relink.
For subdirectory deployments, prefer setting rootDirectory via the environment skill, then deploy normally with railway up.
After Deploy
Detach mode
Deploying to <service>...
Use deployment skill to check build status (with --lines flag).
CI mode
Build logs stream inline. If build fails, the error will be in the output.
Do NOT run railway logs --build after CI mode - the logs already streamed. If you need
more context, use deployment skill with --lines flag (never stream).
Composability
- Check status after deploy: Use
serviceskill - View logs: Use
deploymentskill - Fix config issues: Use
environmentskill - Redeploy after config fix: Use
environmentskill
Error Handling
No Project Linked
No Railway project linked. Run `railway link` first.
No Service Linked
No service linked. Use --service flag or run `railway service` to select one.
Build Failure (CI mode)
The build logs already streamed - analyze them directly from the railway up --ci output.
Do NOT run railway logs after CI mode (it streams forever without --lines).
Common issues:
- Missing dependencies → check package.json/requirements.txt
- Build command wrong → use environment skill to fix
- Dockerfile issues → check dockerfile path
How to use deploy on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add deploy
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches deploy from GitHub repository railwayapp/railway-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate deploy. Access the skill through slash commands (e.g., /deploy) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
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
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★25 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
Keeps context tight: deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kwame Sethi· Dec 4, 2024
deploy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Camila Gonzalez· Nov 23, 2024
deploy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Oshnikdeep· Nov 19, 2024
Registry listing for deploy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Luis Huang· Oct 14, 2024
Registry listing for deploy matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Oct 10, 2024
deploy reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Anika Harris· Sep 9, 2024
deploy has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ama Menon· Sep 5, 2024
Useful defaults in deploy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Rahul Santra· Sep 1, 2024
I recommend deploy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Luis Singh· Aug 28, 2024
Solid pick for teams standardizing on skills: deploy is focused, and the summary matches what you get after install.
showing 1-10 of 25