CtrlK
BlogDocsLog inGet started
Tessl Logo

assistant-ui-streaming

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

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

The body is a tight, executable reference: lean prose, copy-paste code for the main streaming patterns, a useful decision tree, and a well-structured references section pointing to real bundle files. The only gap is the absence of explicit validation/feedback checkpoints, which is less critical for this non-destructive reference skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — a one-line overview, executable code blocks, and a gotchas list with no padding or explanation of basic streaming concepts, matching the anchor 5 example.

5 / 5

Actionability

Multiple copy-paste-ready TypeScript/TSX blocks cover the common cases (custom response with tool calls, useLocalRuntime fetch loop, debugging decode loop) plus an install command and concrete gotcha fixes.

5 / 5

Workflow Clarity

The 'When to Use' decision tree gives clear routing between the Vercel AI SDK and custom assistant-stream paths and sections are well organized, but as a reference-style skill it lacks explicit validation checkpoints, keeping it just below anchor 5.

4 / 5

Progressive Disclosure

A concise overview points to three real, one-level-deep reference files (data-stream.md, assistant-transport.md, encoders.md), each labeled with a one-line description, matching the anchor 5 clear-overview-with-well-signaled-references pattern.

5 / 5

Total

19

/

20

Passed

Description

70%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 successfully answers both what the skill does and when to use it with natural trigger phrases, using appropriate third-person voice. It is held back from the top band by slightly broad action categories and minor overlap risk with generic streaming skills.

Suggestions

Replace the soft 'Guide for' opening with concrete verbs, e.g. 'Stream AI backend responses via the assistant-stream package: build custom streaming responses, wire up useLocalRuntime, and decode data streams.'

Add package-level trigger terms such as 'assistant-stream', 'assistant-ui', or '@assistant-ui/react' so users referencing those names naturally match this skill.

Sharpen the 'when' clause with a disambiguating boundary, e.g. 'Use when building custom streaming backends; if you only use the Vercel AI SDK, use toUIMessageStreamResponse instead.'

DimensionReasoningScore

Specificity

Names the domain (assistant-stream, streaming protocols) and three action areas (implementing backends, custom protocols, debugging), but these are broad categories rather than crisply concrete actions, so it sits at anchor 3 rather than 4.

3 / 5

Completeness

Both a clear 'what' ('Guide for assistant-stream package and streaming protocols') and an explicit 'when' ('Use when implementing streaming backends, custom protocols, or debugging stream issues') are present, but the 'what' is softer than a crisp action list so it does not reach anchor 5.

4 / 5

Trigger Term Quality

Natural developer phrases like 'streaming backends', 'custom protocols', and 'debugging stream issues' give good keyword coverage, though a few common synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

The assistant-stream package niche is mostly distinct, with only minor overlap risk against closely related generic AI-SDK streaming skills rather than the clear no-overlap niche of anchor 5.

4 / 5

Total

15

/

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.

Validation15 / 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
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.