Push code to Railway with railway up , supporting detach and CI streaming modes.
Works with
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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeployExecute the skills CLI command in your project's root directory to begin installation:
Fetches deploy from railwayapp/railway-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate deploy. Access via /deploy in your agent's command palette.
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.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
225
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
225
stars
Deploy code from the current directory to Railway using railway up.
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:
Starts deploy and returns immediately. Use for most deploys.
railway up --detach -m "Deploy description here"
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:
Default is linked service. To deploy to a different service:
railway up --detach --service backend -m "Deploy description here"
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.
| 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) |
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.
Deploying to <service>...
Use deployment skill to check build status (with --lines flag).
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).
service skilldeployment skillenvironment skillenvironment skillNo Railway project linked. Run `railway link` first.
No service linked. Use --service flag or run `railway service` to select one.
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:
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
deploy is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
deploy reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for deploy matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for deploy matched our evaluation — installs cleanly and behaves as described in the markdown.
deploy reduced setup friction for our internal harness; good balance of opinion and flexibility.
deploy has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in deploy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend deploy for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: deploy is focused, and the summary matches what you get after install.
showing 1-10 of 25