View, manage, and troubleshoot Railway deployments with logs, redeploy, and removal commands.
Works with
List deployments and view deploy or build logs with filtering by level, text search, time range, or specific deployment ID
Redeploy the most recent deployment or restart containers without rebuilding to pick up external resource changes
Remove deployments (stops the service but keeps it intact; use the environment skill to delete services entirely)
Supports JSON output for all commands an
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondeploymentExecute the skills CLI command in your project's root directory to begin installation:
Fetches deployment 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 deployment. Access via /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
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
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 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 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:
deploy skillstatus skillenvironment skillnew skillNo 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.
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
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
deployment is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: deployment is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for deployment matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: deployment is the kind of skill you can hand to a new teammate without a long onboarding doc.
deployment reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for deployment matched our evaluation — installs cleanly and behaves as described in the markdown.
deployment reduced setup friction for our internal harness; good balance of opinion and flexibility.
deployment is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for deployment matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in deployment — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 42