What problem does it solve? Connecting the Hatchet CLI to the Alliance Railway deployment is error-prone: tokens embed stale internal URLs, there is no login command, and local workers confuse the API route with the gRPC endpoint. This Skill provides the exact profile setup, token handling, and read-only inspection workflow for the railway-monorepo instance. ## Core Features & Use Cases - Safe CLI profile setup: Create the railway-monorepo profile using fnox/mise token injection with explicit API and TLS overrides, without ever printing the token. - Read-only run inspection: List workflows, list failed runs, inspect individual runs, and launch the Hatchet TUI against http://railway-monorepo:11744. - Troubleshooting guidance: Diagnose stale token-derived URLs, tsmesh/DNS failures, and the distinction between the UI/API route and the hardcoded gRPC endpoint hatchet.railway.internal:7077 used by the BullQueue worker. - Use Case: You need to check why jobs failed last week on the Alliance Railway Hatchet instance. The Skill walks you through verifying the route health, injecting the token via fnox, and running hatchet runs list with the correct overrides. ## Quick Start Ask the assistant to list failed Hatchet runs from the last 7 days on the railway-monorepo profile using the fnox-injected token and the tsmesh API overrides.