streaming

Response streaming configuration and real-time output

Quality

43%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/streaming/SKILL.md

Quality

Content

64%

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

This is a competent API reference with concrete, executable code examples and clear command syntax. Its main weaknesses are moderate verbosity from redundant sections (chat commands and TypeScript API overlap significantly), lack of error handling or validation guidance, and the monolithic structure that could benefit from splitting detailed API reference into a separate file.

Suggestions

Remove redundant inline comments that restate the obvious (e.g., '// Enable streaming' above `streaming.enable()`) and consolidate overlapping chat command / TypeScript sections.

Add error handling examples and a validation step showing how to verify streaming is configured correctly (e.g., a test command or health check).

Move the detailed TypeScript API reference and platform limits table to a separate REFERENCE.md, keeping SKILL.md as a concise quick-start with links.

Dimension	Reasoning	Score
Conciseness	The content is reasonably organized but includes some redundancy—the chat commands section largely mirrors the TypeScript API section, and comments like '// Enable streaming' next to `streaming.enable()` add no value. The platform limits table is useful but the best practices section states obvious things Claude would already know.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples with concrete configuration objects, method calls, and specific parameter values. The chat commands are copy-paste ready with clear syntax.	3 / 3
Workflow Clarity	This is primarily an API reference rather than a multi-step workflow, so sequencing is less critical. However, there's no guidance on when to use streaming vs not (beyond 'don't stream OK'), no error handling, and no validation steps for verifying streaming is working correctly after configuration.	2 / 3
Progressive Disclosure	The content is structured with clear sections and a table, but it's a fairly long monolithic file. The platform limits and detailed API methods could be split into separate reference files, with the SKILL.md serving as a concise overview with links.	2 / 3
	Total	9 / 12 Passed

Description

22%

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

This description is too terse and vague to effectively guide skill selection. It names a general domain (streaming) but fails to list concrete actions, provide trigger terms users would naturally use, or include any 'Use when...' guidance. It would likely be overlooked or confused with other real-time or configuration-related skills.

Suggestions

List specific concrete actions the skill performs, e.g., 'Configures response streaming for APIs, enables server-sent events (SSE), manages chunked transfer encoding, and handles real-time output buffering.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about streaming responses, real-time output, SSE, chunked responses, or progressive rendering.'

Include common keyword variations users might say, such as 'stream', 'live output', 'SSE', 'chunked transfer', 'progressive loading', or 'real-time responses'.

Dimension	Reasoning	Score
Specificity	The description is vague — 'configuration and real-time output' does not list any concrete actions. It doesn't say what specific tasks the skill performs (e.g., enable streaming, configure chunk sizes, handle SSE connections).	1 / 3
Completeness	The description weakly addresses 'what' (streaming configuration) but provides no 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also too vague to merit a 2.	1 / 3
Trigger Term Quality	'Streaming' and 'real-time output' are somewhat relevant keywords a user might use, but the description lacks common variations or natural phrases like 'stream responses', 'SSE', 'chunked transfer', 'live output', or 'progressive rendering'.	2 / 3
Distinctiveness Conflict Risk	'Response streaming' is somewhat specific to a domain, but 'configuration and real-time output' is broad enough to overlap with skills related to WebSockets, server-sent events, general API configuration, or real-time data processing.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 2 months ago

Table of Contents

Discovery Implementation Validation

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.