railway-deployThis 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.
Install via ClawdBot CLI:
clawdbot install dbanys/railway-deployDeploy code from the current directory to Railway using railway up.
Always use the -m flag with a descriptive commit message summarizing what's being deployed:
railway up --detach -m "Add user authentication endpoint"Good commit messages:
Starts deploy and returns immediately. Use for most deploys.
railway up --detach -m "Deploy description here"Streams build logs until complete. Use when user wants to watch the build or needs to debug issues.
railway up --ci -m "Deploy description here"When to use CI mode:
Default is linked service. To deploy to a different service:
railway up --detach --service backend -m "Deploy description here"Deploy to a project without linking first:
railway up --project <project-id> --environment production --detach -m "Deploy description here"Requires both --project and --environment flags.
| Flag | Description |
|------|-------------|
| -m, --message | Commit message describing the deploy (always use this) |
| -d, --detach | Don't attach to logs (default) |
| -c, --ci | Stream build logs, exit when done |
| -s, --service | Target service (defaults to linked) |
| -e, --environment | Target environment (defaults to linked) |
| -p, --project | Target project (requires --environment) |
| [PATH] | Path to deploy (defaults to current directory) |
Railway CLI walks UP the directory tree to find a linked project. If you're in a subdirectory of a linked project, you don't need to relink.
For subdirectory deployments, prefer setting rootDirectory via the environment skill, then deploy normally with railway up.
Deploying to <service>...Use deployment skill to check build status (with --lines flag).
Build logs stream inline. If build fails, the error will be in the output.
Do NOT run railway logs --build after CI mode - the logs already streamed. If you need
more context, use deployment skill with --lines flag (never stream).
service skilldeployment skillenvironment skillenvironment skillNo Railway project linked. Run `railway link` first.No service linked. Use --service flag or run `railway service` to select one.The build logs already streamed - analyze them directly from the railway up --ci output.
Do NOT run railway logs after CI mode (it streams forever without --lines).
Common issues:
AI Usage Analysis
Analysis is being generated… refresh in a few seconds.
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
Full desktop computer use for headless Linux servers. Xvfb + XFCE virtual desktop with xdotool automation. 17 actions (click, type, scroll, screenshot, drag,...
Essential Docker commands and workflows for container management, image operations, and debugging.
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.
Monitor topics of interest and proactively alert when important developments occur. Use when user wants automated monitoring of specific subjects (e.g., product releases, price changes, news topics, technology updates). Supports scheduled web searches, AI-powered importance scoring, smart alerts vs weekly digests, and memory-aware contextual summaries.