What problem does it solve? Building live progress UIs for background tasks usually means hand-rolling WebSockets or polling loops. This Skill shows how to consume Trigger.dev's realtime API from React/Next.js/Remix so run status, metadata, and AI token streams appear in the browser without polling infrastructure. ## Core Features & Use Cases - Realtime run subscriptions: Use runs.subscribeToRun or the useRealtimeRun hook from @trigger.dev/react-hooks to track live run state, with skipColumns to avoid shipping unused payload/output fields. - Stream consumption: Render AI/text streams in React with useRealtimeStream for token-by-token output. - Browser-side triggering: Trigger tasks with useTaskTrigger or useRealtimeTaskTrigger using single-use tokens minted via auth.createTriggerPublicToken, and scope read access with auth.createPublicToken. - Use Case: A Next.js app shows a status badge and live LLM token stream for a document-processing task: the backend mints a scoped public token, the client component subscribes with useRealtimeRun, and a trigger button starts new runs. ## Quick Start Ask the AI to wire a Next.js client component that subscribes to a Trigger.dev run with useRealtimeRun and renders a live status badge using a scoped public token.