Deploy code from the current directory to Railway using railway up.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrailway-deployExecute the skills CLI command in your project's root directory to begin installation:
Fetches railway-deploy from davila7/claude-code-templates 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 railway-deploy. Access via /railway-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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
24.2K
stars
Deploy code from the current directory to Railway using railway up.
Starts deploy and returns immediately. Use for most deploys.
railway up --detach
Streams build logs until complete. Use when user wants to watch the build or needs to debug issues.
railway up --ci
When to use CI mode:
Default is linked service. To deploy to a different service:
railway up --detach --service backend
Deploy to a project without linking first:
railway up --project <project-id> --environment production --detach
Requires both --project and --environment flags.
| Flag | Description |
|---|---|
-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 railway-environment skill, then deploy normally with railway up.
Deploying to <service>...
Use railway-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 railway-deployment skill with --lines flag (never stream).
No 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:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
Keeps context tight: railway-deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added railway-deploy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
railway-deploy has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: railway-deploy is focused, and the summary matches what you get after install.
Keeps context tight: railway-deploy is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added railway-deploy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
railway-deploy has been reliable in day-to-day use. Documentation quality is above average for community skills.
railway-deploy fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added railway-deploy from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in railway-deploy — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 31