agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-railway-deployment/SKILL.md

role-railway-deployment

Skill2 starsChanged 3 months agoMITView on GitHub

Railway.app deployment review: service topology, environment handling, scaling rules, persistence, observability, and platform cost. Use for Railway-specific deployment planning or auditing.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check secrets, env separation, service linking before tuning scale.

    line 27
  2. Distinctive:

    Call out Railway-specific limits or hidden cost multipliers.

    line 29
  3. Distinctive:

    Keep review Railway-specific, not generic cloud advice.

    line 43
  4. Distinctive:

    Treat rollback and health checks as release blockers when weak.

    line 44
  5. Distinctive:

    Do not change application ownership under cover of deployment review.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Map service graph, ingress paths, data stores, dependencies.
  2. Check secrets, env separation, service linking before tuning scale.
  3. Review persistence, health checks, deploy flow, rollback path together.
  4. Call out Railway-specific limits or hidden cost multipliers.
  5. 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 watch

Anti-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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.