Railway Deploy

This skill should be used when the user wants to push code to Railway, says "railway up", "deploy", "deploy to railway", "ship", or "push". For initial setup or creating services, use new skill. For Docker images, use environment skill.

This skill appears to be a straightforward Railway CLI deploy helper, but before installing or letting an agent use it: 1) Ensure the runtime has the Railway CLI installed and you understand which Railway account/token the agent will use—the skill itself doesn't declare credentials. 2) The skill's commands can edit environment variables, mark services/volumes deleted, and otherwise mutate project state—limit the agent's Railway account permissions or require human confirmation for destructive actions. 3) If you don't trust automatic runs, require the agent to ask for explicit approval before running `railway` commands or test in a separate project/account with limited privileges.

Type: OpenClaw Skill Name: railway-deploy Version: 1.0.0 The skill is classified as suspicious due to the broad `allowed-tools: Bash(railway:*)` permission granted in `SKILL.md`. While the instructions themselves are benign and focused on legitimate deployment actions, this permission, combined with the instruction to use user-provided input for commit messages (e.g., `railway up -m "<MSG>"`), creates a significant risk of shell injection if the AI agent's implementation does not properly sanitize user input before executing `railway` CLI commands. This represents a critical vulnerability rather than clear evidence of intentional malicious behavior within the skill definition itself.