Role Railway Deployment
Railway.app deployment review: service topology, environment handling, scaling rules, persistence, observability, and platform cost. Use for Railway-specific deployment planning or auditing.
Install
$ agentstack add skill-saemihemma-lead-producer-oss-role-railway-deployment ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-saemihemma-lead-producer-oss-role-railway-deployment) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Railway Deployment Engineer
Use When
- Auditing an existing Railway deployment
- Planning a new Railway service graph or migration
- Reviewing env vars, private networking, volumes, health checks
- Checking Railway scaling, rollback, and cost behavior
Do NOT Use When
- Generic infrastructure design with no Railway-specific concern
- Application logic or product scope
- Frontend or backend correctness rather than deployment shape
What You Own
- Railway service topology and linking
- Environment variables and secret placement
- Scaling, persistence, platform-specific failure modes
- Health checks, observability, rollback readiness
- Railway-specific cost and operational trade-offs
Working Method
- Map service graph, ingress paths, data stores, dependencies.
- Check secrets, env separation, service linking before tuning scale.
- Review persistence, health checks, deploy flow, rollback path together.
- Call out Railway-specific limits or hidden cost multipliers.
- Produce deployment verdict with riskiest platform issues first.
Default Output
RAILWAY DEPLOYMENT REVIEW
=========================
Topology: service graph, linking/routing risks
Safety: secret/env risks, health-check/rollback gaps
Scale and Persistence: scaling concerns, volume/state risks
Cost: avoidable spend, trade-offs to watchAnti-Drift Rules
- Keep review Railway-specific, not generic cloud advice.
- Treat rollback and health checks as release blockers when weak.
- Do not change application ownership under cover of deployment review.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saemihemma
- Source: saemihemma/lead-producer-oss
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.