deployment — Claude Code skill for Railway deploys
A Claude skill that lets the agent run Railway deployment tasks: read logs, restart, redeploy, take a deploy down. Handy when a service crashes or you need deploy history.
npx claude-code-templates@latest --skill railway/deploymentWhat deployment does
The skill covers the lifecycle of a deployment that already exists on Railway. The agent can list deploys with their IDs and statuses, pull build or runtime logs, restart a container, redeploy the latest build, and take the current deploy down with railway down. What sits inside is guidance for Railway CLI calls, and the allowed tool is limited to Bash(railway:*), so everything goes through that binary.
Log filtering works by level and text: railway logs --lines 50 --filter "@level:error" --json. Time windows come from --since and --until, either relative (30s, 5m, 2h, 1d, 1w) or ISO 8601. Plain railway logs returns the last successful deploy; add --latest to see the current one. A deployment ID goes in as a positional argument — --deployment is a boolean that switches to deploy logs instead of --build.
Railway CLI has to be there first: the skill lists railway-cli as a dependency, and without it the commands go nowhere. One boundary matters. railway down stops a deploy while the service stays in place, so reaching for it to kill a service leaves you with a service that has nothing running. Full service deletion belongs to the railway-environment skill with isDeleted: true.
What it helps with
- read logs from a failed deploy and trace the cause
- restart a container without rebuilding after external resources change
- pull deploy history with IDs and statuses
- redeploy the latest build after a config change
- take a deploy down while keeping the service
Example prompts for the agent
- Show the last 100 log lines for the
backendservice and flag the errors - Restart the
apiservice deploy without rebuilding - Take down the current deploy for the
webservice
How to install deployment
1claude-code-templates
npx claude-code-templates@latest --skill railway/deployment2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill deployment -a claude-code3Manually: put the files in place
~/.claude/skills/deployment/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/deployment/
Manually: put the files in place
.agents/skills/deployment/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/deployment/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates deployment2Manually: put the files in place
.github/skills/deployment/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/railway/deploymentManually: put the files in place
.devin/skills/deployment/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about deployment
How do I install deployment in Claude Code?
Run npx claude-code-templates@latest --skill railway/deployment. Or use npx skills add davila7/claude-code-templates --skill deployment -a claude-code. The skill file then lives at ~/.claude/skills/deployment/SKILL.md.
What does the deployment skill do?
It manages Railway deployments: listing and history, deploy and build logs, restart, redeploy, and taking a deploy down. All of it runs through Railway CLI.
How is railway down different from deleting a service?
railway down stops the current deploy but leaves the service in place. Deleting a service entirely is the job of the railway-environment skill with isDeleted: true.
