Manage existing Railway deployments: list, view logs, redeploy, or remove.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrailway-deploymentExecute the skills CLI command in your project's root directory to begin installation:
Fetches railway-deployment 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-deployment. Access via /railway-deployment 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
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Manage existing Railway deployments: list, view logs, redeploy, or remove.
Important: "Remove deployment" (railway down) stops the current deployment but keeps the service. To delete a service entirely, use the railway-environment skill with isDeleted: true.
railway deployment list --limit 10 --json
Shows deployment IDs, statuses, and metadata. Use to find specific deployment IDs for logs or debugging.
railway deployment list --service backend --limit 10 --json
railway logs --lines 100 --json
In non-interactive mode, streaming is auto-disabled and CLI fetches logs then exits.
railway logs --build --lines 100 --json
For debugging build failures or viewing build output.
By default railway logs shows the last successful deployment. Use --latest for current:
railway logs --latest --lines 100 --json
# Errors only
railway logs --lines 50 --filter "@level:error" --json
# Text search
railway logs --lines 50 --filter "connection refused" --json
# Combined
railway logs --lines 50 --filter "@level:error AND timeout" --json
# Logs from last hour
railway logs --since 1h --lines 100 --json
# Logs between 30 and 10 minutes ago
railway logs --since 30m --until 10m --lines 100 --json
# Logs from specific timestamp
railway logs --since 2024-01-15T10:00:00Z --lines 100 --json
Formats: relative (30s, 5m, 2h, 1d, 1w) or ISO 8601 timestamps.
Deploy logs:
railway logs <deployment-id> --lines 100 --json
Build logs:
railway logs --build <deployment-id> --lines 100 --json
Get deployment ID from railway deployment list.
Note: The deployment ID is a positional argument, NOT --deployment <id>. The --deployment flag is a boolean that selects deploy logs (vs --build for build logs).
Redeploy the most recent deployment:
railway redeploy --service <name> -y
The -y flag skips confirmation. Useful when:
Restart without rebuilding (picks up external resource changes):
railway restart --service <name> -y
Use when external resources (S3 files, config maps) changed but code didn't.
Takes down the current deployment. The service remains but has no running deployment.
# Remove deployment for linked service
railway down -y
# Remove deployment for specific service
railway down --service web -y
railway down --service api -y
This is what users mean when they say "remove deploy", "take down", or "stop the deployment".
Note: This does NOT delete the service. To delete a service entirely, use the railway-environment skill with isDeleted: true.
| Flag | Description |
|---|---|
-s, --service <NAME> |
Service name or ID |
-e, --environment <NAME> |
Environment name or ID |
--limit <N> |
Max deployments (default 20, max 1000) |
--json |
JSON output |
| Flag | Description |
|---|---|
-s, --service <NAME> |
Service name or ID |
-e, --environment <NAME> |
Environment name or ID |
-d, --deployment |
Show deploy logs (default, boolean flag) |
-b, --build |
Show build logs (boolean flag) |
-n, --lines <N> |
Number of lines (required) |
-f, --filter <QUERY> |
Filter using query syntax |
--since <TIME> |
Start time (relative or ISO 8601) |
--until <TIME> |
End time (relative or ISO 8601) |
--latest |
Most recent deployment (even if failed) |
--json |
JSON output |
[DEPLOYMENT_ID] |
Specific deployment (optional) |
| Flag | Description |
|---|---|
-s, --service <NAME> |
Service name or ID |
-y, --yes |
Skip confirmation |
| Flag | Description |
|---|---|
-s, --service <NAME> |
Service name or ID |
-y, --yes |
Skip confirmation |
| Flag | Description |
|---|---|
-s, --service <NAME> |
Service name or ID |
-e, --environment <NAME> |
Environment name or ID |
-y, --yes |
Skip confirmation |
When showing logs:
No service linked. Run `railway service` to select one.
No deployments found. Deploy first with `railway up`.
Deployment may be too old (log retention limits) or service hasn't produced output.
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
I recommend railway-deployment for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: railway-deployment is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in railway-deployment — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for railway-deployment matched our evaluation — installs cleanly and behaves as described in the markdown.
railway-deployment fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
railway-deployment reduced setup friction for our internal harness; good balance of opinion and flexibility.
railway-deployment is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added railway-deployment from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: railway-deployment is focused, and the summary matches what you get after install.
railway-deployment is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 49