CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

assistant-ui-streaming

Guide for assistant-stream package and streaming protocols. Use when implementing streaming backends, custom protocols, or debugging stream issues.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/assistant-ui/assistant-ui-streaming/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured reference skill: executable code examples, a clear when-to-use decision tree, and clean one-level-deep disclosure into three verified reference files. The only meaningful gap is that the two main code examples don't join into a complete end-to-end flow (invented line protocol in the runtime example, hardcoded text in the response example).

DimensionReasoningScore

Conciseness

The body is lean and code-first with almost no padding — sections like "Custom Streaming Response", "With useLocalRuntime", and "Common Gotchas" contain only a one-line framing sentence plus executable code or terse bullets. It assumes Claude's competence (no explanation of what streaming or fetch is) and every section earns its place, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

The code examples are real and executable — createAssistantStreamResponse with tool calls, a full useLocalRuntime generator, and a DataStreamDecoder debugging loop — matching 'Mostly executable guidance; concrete code with minor gaps'. Not a 5: the custom-response example hardcodes 'Hello world' instead of showing a real backend source, and the useLocalRuntime example invents a newline-delimited chunk protocol with no matching encoder shown, so the two examples don't compose into a working end-to-end flow.

4 / 5

Workflow Clarity

The "When to Use" decision tree ("Using Vercel AI SDK? Yes → toUIMessageStreamResponse() / No → assistant-stream") gives clear routing, and the Debugging/Gotchas sections provide concrete diagnostic steps keyed to symptoms ("Stream not updating UI" → check Content-Type, CORS). This matches 'clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because the debugging guidance is a checklist rather than an explicit validate-then-fix loop; not a 3 because the decision routing and symptom-to-cause mapping are explicit and unambiguous.

4 / 5

Progressive Disclosure

The References section cleanly signals three one-level-deep files (data-stream.md, assistant-transport.md, encoders.md) with one-line descriptions, and all three exist in the bundle with no further nesting (verified: no links to other .md files inside them). The body keeps only quick-start material inline and pushes format details to the reference files, matching 'Clear overview with well-signaled one-level-deep references; content appropriately split'.

5 / 5

Total

18

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has a clear when-clause and a distinct niche around the assistant-stream package, but the 'what' is under-specified ('Guide for...') and trigger coverage lacks common synonyms like SSE or token streaming. It reads as competent but generic guidance rather than a concrete capability list.

Suggestions

Replace 'Guide for' with concrete capability verbs, e.g. 'Create custom streaming responses with createAssistantStreamResponse, integrate useLocalRuntime, and decode/debug AI SDK and assistant-ui stream formats.'

Add natural trigger synonyms users would actually say, such as 'SSE', 'token streaming', 'stream not updating', or 'AI SDK streaming', to broaden trigger coverage.

Mention the key integrations by name (assistant-ui, Vercel AI SDK) in the description to sharpen distinctiveness against generic streaming skills.

DimensionReasoningScore

Specificity

"Guide for assistant-stream package and streaming protocols" names the domain, and "implementing streaming backends, custom protocols, or debugging stream issues" lists 2-3 use contexts, but the skill's actual capabilities (creating streaming responses, decoding streams, integrating runtimes) are never stated — comparable to 'Names domain and 1-2 concrete actions, but not comprehensive'. Not a 4 because 'Guide for' is generic about what the skill does rather than listing several specific actions.

3 / 5

Completeness

Both parts are present: what ("Guide for assistant-stream package and streaming protocols") and when ("Use when implementing streaming backends, custom protocols, or debugging stream issues"). Matches 'Has both what and when; when could be more explicit or specific' — the 'what' is somewhat vague ('Guide for') and the when-clause could name more concrete triggers. Not a 5 because neither part is fully concrete; not a 3 because the when-clause is explicit, not merely implied.

4 / 5

Trigger Term Quality

"streaming backends", "custom protocols", and "debugging stream issues" are relevant phrases users might say, but common variations are missing — no mention of SSE, token streaming, chat streams, AI SDK specifics, or "stream not updating" style debugging phrasing. Matches 'Some relevant keywords but missing common variations or synonyms'; not a 4 because the coverage is noticeably thin rather than good-with-few-gaps.

3 / 5

Distinctiveness Conflict Risk

"assistant-stream package" carves out a clear niche that would not fire for unrelated skills, and the scope is limited to streaming protocols. Minor overlap risk remains with closely related skills (generic SSE/streaming or AI SDK skills), matching 'Mostly distinct; minor overlap risk with closely related skills'. Not a 5 because 'streaming backends' and 'debugging stream issues' alone could also match a general streaming skill.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

compozy/compozy

Path

.agents/skills/assistant-ui/assistant-ui-streaming/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.