Initial commit: OpenClaw Skill Collection

6 custom skills (assign-task, dispatch-webhook, daily-briefing,
task-capture, qmd-brain, tts-voice) with technical documentation.
Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.

openclaw-knowhow-skill/docs/infrastructure/railway.md

@@ -0,0 +1,33 @@
+# Deploy on Railway
+
+## Overview
+This guide covers deploying OpenClaw on Railway using a one-click template with browser-based configuration.
+
+## Key Setup Steps
+The deployment process involves four main actions:
+1. Click the Railway deploy button
+2. Attach a Volume at `/data`
+3. Configure required environment variables
+4. Enable HTTP Proxy on port 8080
+
+## Access Points
+Once deployed, you'll have two primary interfaces:
+- Setup wizard at `/setup` (password-protected)
+- Control UI at `/openclaw` (main application interface)
+
+## Essential Configuration Variables
+Several environment variables must be set on the Railway service:
+- `SETUP_PASSWORD` (mandatory for security)
+- `PORT=8080` (must align with networking configuration)
+- `OPENCLAW_STATE_DIR=/data/.openclaw` (for persistent configuration)
+- `OPENCLAW_WORKSPACE_DIR=/data/workspace` (for persistent data)
+- `OPENCLAW_GATEWAY_TOKEN` (treat as administrative credential)
+
+## Chat Platform Integration
+The setup wizard supports adding credentials for:
+- **Telegram**: Obtain tokens via @BotFather using `/newbot`
+- **Discord**: Create bot tokens through the developer portal and enable Message Content Intent
+- **Slack**: Token configuration available during setup
+
+## Data Protection
+A backup export feature at `/setup/export` allows you to download your complete OpenClaw state and workspace, facilitating migration to alternative hosting platforms without data loss.