What problem does it solve? Updating a production OmniRoute instance behind a reverse proxy is fragile: Turbopack builds exhaust RAM, killed builds wipe the standalone output, and dev-mode HMR breaks login behind the proxy. This Skill encodes the exact safe update, verification, and rollback procedure so any agent can maintain the deployment without breaking it. ## Core Features & Use Cases - Idiot-proof update script: scripts/update-via-proxy.sh performs backup, git upgrade to the latest upstream release branch, re-pinning of BASE_PATH/supervisor/env config, webpack production build with RAM guards, and ordered restarts. - Deep verification: scripts/verify.sh plus a Playwright-based verify-login.mjs check supervisor state, basePath pins, proxy routes, local/public API health, and that the login page actually hydrates a password form. - Hermes slash commands: a plugin exposes /omni update, /omni verify, and /omni status for Telegram/CLI operation. - Use Case: After an upstream OmniRoute release, run /omni update to pull the release branch, rebuild with webpack (never Turbopack), restart services, and confirm the proxied UI and http://127.0.0.1:20128/omniroute/v1 API both work. ## Quick Start Ask the agent to update OmniRoute and verify the deployment, which runs the update-via-proxy script followed by the verification checks.