メニュー
Interact with Railway deployments — check status, view logs, redeploy services, and manage environment variables.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dustland/openviber --skill railwayコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
SOC 職業分類に基づく
Run OpenAI Codex CLI for autonomous software engineering tasks via non-interactive `codex exec` with chat-friendly outputs.
Use the Cursor CLI (agent) for software engineering tasks. Includes installation, auth, commands, terminal-based automation, and best practices for AI coding workflows.
Run Google Gemini CLI for autonomous coding and general tasks via headless mode with chat-friendly outputs.
| name | railway |
| version | 1.0.0 |
| description | Interact with Railway deployments — check status, view logs, redeploy services, and manage environment variables. |
Manage Railway deployments directly from Viber. Uses the Railway CLI (railway) for deployment operations.
Install Railway CLI:
pnpm add -g @railway/cli
# or
brew install railway
Then authenticate:
railway login
Link your project (run once in the project directory):
railway link
railway_status — Get deployment status for the linked project or a specific servicerailway_logs — View recent runtime logsrailway_deploy — Trigger a redeploymentrailway_deployments — List recent deployments with status (SUCCESS/FAILED/BUILDING)railway_build_logs — Fetch build logs for a specific deployment by ID (for diagnosing build failures)railway_run — Run any Railway CLI command directlyservice (optional): Service name to check (defaults to all services)cwd (optional): Working directory (if unlinked/mismatched, auto-discovery will try matching repo-related project/service contexts)service (optional): Service name to get logs forlines (optional): Number of log lines (default: 50, max: 500)deploymentId (optional): Deployment ID to fetch logs for (if omitted, uses latest deployment)cwd (optional): Working directory (if unlinked/mismatched, auto-discovery will try matching repo-related project/service contexts)service (optional): Service to redeploycwd (optional): Working directory (if unlinked/mismatched, auto-discovery will try matching repo-related project/service contexts)cwd (optional): Working directory (if unlinked/mismatched, auto-discovery will try matching repo-related project/service contexts)deploymentId (required): Deployment ID (UUID from railway_deployments output)cwd (optional): Working directory (if unlinked/mismatched, auto-discovery will try matching repo-related project/service contexts)command (required): Railway CLI subcommand and arguments (e.g. variables list)cwd (optional): Working directory (if unlinked/mismatched, auto-discovery will try matching repo-related project/service contexts)Use this skill when user intent is:
Examples:
railway_status({ service: "web" })
railway_logs({ service: "web", lines: 100 })
railway_deploy({ service: "web" })
railway_deployments({})
railway_build_logs({ deploymentId: "abc-123..." })
railway_run({ command: "variables list" })
When a directory is not Railway-linked or linked to the wrong project, this skill will:
railway list --jsonThis allows the agent to keep trying across org/project/service combinations instead of failing on the first context mismatch.