← Search

LLM streaming response handler — production SSE streaming UIs with cancellation and error recovery
Dev 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 6713fc7
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a frontend/backend project that calls an LLM…

LLM streaming response handler — production SSE streaming UIs with cancellation and error recovery

Build production-grade LLM streaming UIs with Server-Sent Events — token-by-token display, AbortController cancellation, error recovery, React hooks, Next.js server patterns, and a production checklist

At a glance
What
Build production-grade LLM streaming UIs with Server-Sent Events — token-by-token display, AbortController cancellation, error recovery, React hooks, Next.js server patterns, and a production checklist
Cost
Free
Needs
a frontend/backend project that calls an LLM streaming API (OpenAI, Anthropic, or similar) — the skill is an implementation guide the agent follows, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

LLM streaming response handler — production SSE streaming UIs with cancellation and error recovery is a free Muse skill that guides building streaming interfaces for LLM, covering why SSE beats WebSockets for streaming, the formats of OpenAI, Anthropic, and Vercel AI SDK, five anti-patterns with fixes, and patterns including an SSE handler, a React useStreaming hook, and a Next.js route.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 6713fc7

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a frontend/backend project that calls an LLM streaming API (OpenAI, Anthropic, or similar) — the skill is an implementation guide the agent follows, not software Install "LLM streaming response handler — production SSE streaming UIs with cancellation and error recovery" for me. It gives my agent @curiositech's streaming guide: choose SSE for one-way LLM streaming, implement token-by-token display (never buffer before display), add AbortController cancellation, error states with retry, cleanup on unmount to avoid memory leaks, typing indicators, and use the copy-ready patterns — basic SSE stream handler, React useStreaming hook, Next.js edge-runtime API route — then run the 12-point production checklist (rate limiting, token tracking, streaming fallback, accessibility, mobile targets, network recovery, max length, cost estimation). MIT-licensed. Repository: https://raw.githubusercontent.com/curiositech/some_claude_skills/6713fc7a6451c8dee5903b98cd2063ff4cbf7317/.claude/skills/llm-streaming-response-handler/SKILL.md Pinned version: install the code at commit 6713fc7a6451c8dee5903b98cd2063ff4cbf7317 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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 "llm-streaming-response-handler". 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. wire the useStreaming hook or SSE handler into my chat UI and API route; nothing else — it's a methodology). 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.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 6713fc7 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
6713fc7 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.