Trigger.dev realtime: live run updates and streams in your frontend
The consumer side of Trigger.dev runs — subscribe to live run state, render AI/text streams, trigger tasks from the browser, and mint scoped frontend tokens
- What
- The consumer side of Trigger.dev runs — subscribe to live run state, render AI/text streams, trigger tasks from the browser, and mint scoped frontend tokens
- Cost
- Free
- Needs
- a Trigger.dev project with backend tasks to consume (this is the consumer side — task authoring is a different skill) and the @trigger.dev/sdk + @trigger.dev/react-hooks npm packages in your app — the skill itself needs nothing to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @triggerdotdev's trigger-realtime skill — the consumer side of Trigger.dev's run state and streams (not the backend task authoring; that's trigger-tasks territory). It covers the frontend stack: subscribe to runs in realtime (runs.subscribeToRun and the useRealtimeRun hook), consume metadata and AI/text streams in React (useRealtimeStream), trigger tasks from the browser (useTaskTrigger, useRealtimeTaskTrigger), mint scoped frontend credentials in the backend (auth.createPublicToken for read/subscribe, auth.createTriggerPublicToken for single-use browser triggering — both defaulting to 15-minute expiry), send input back into a running task (useInputStreamSend), complete wait tokens from React (useWaitToken), and subscribe from the backend via async iterators. The flow is always the same: mint a scoped token in the backend, pass it to the frontend, subscribe with a hook. It also carries a common-mistakes list (never trigger from the browser with a read-only Public Access Token, never mint a scopeless token, never poll with useRun, always "use client", always skipColumns payload/output for status badges, guard subscribes on the handle). Honest caveats: the skill is bundled inside @trigger.dev/sdk and read from node_modules, so it matches your installed SDK version; you need a Trigger.dev project with a backend task to consume — frontend-only reading of the skill teaches nothing; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Trigger.dev project with backend tasks to consume (this is the consumer side — task authoring is a different skill) and the @trigger.dev/sdk + @trigger.dev/react-hooks npm packages in your app — the skill itself needs nothing to install Install "Trigger.dev realtime: live run updates and streams in your frontend" for me. It gives my agent @triggerdotdev's trigger-realtime consumer-side skill: subscribe to runs in realtime (runs.subscribeToRun, useRealtimeRun), consume metadata and AI/text streams (useRealtimeStream), trigger tasks from the browser (useTaskTrigger, useRealtimeTaskTrigger), mint scoped frontend credentials in the backend (createPublicToken / createTriggerPublicToken), send input into running tasks, complete wait tokens, and the common-mistakes list. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/triggerdotdev/skills/blob/main/trigger-realtime/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "trigger-realtime". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. have a Trigger.dev project with a backend task, mint scoped tokens in your backend — frontend tokens are useless without scopes and expiry). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.