CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

streaming

Response streaming configuration and real-time output

56

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/streaming/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is highly actionable with executable code and commands and is well organized, but it inlines a lengthy API reference that would be better split into a separate reference file given its size. Progressive disclosure is the main weakness.

Suggestions

Move the bulk TypeScript API reference into a separate file (e.g. references/API.md) and keep only a quick-start example inline in SKILL.md.

Trim redundant inline comments like '// Enable streaming' / '// Disable streaming' that restate the obvious call name.

Consider extracting the platform-limits table into its own reference file and linking to it from a brief overview.

DimensionReasoningScore

Conciseness

The body is mostly lean code and a reference table with no concept lectures, but it carries minor redundant inline comments (e.g. '// Enable streaming' before streaming.enable()) that could be trimmed.

4 / 5

Actionability

It provides fully executable, copy-paste-ready TypeScript examples and concrete slash commands covering the common cases: enable/disable, chunk config, platform limits, and typing indicators.

5 / 5

Workflow Clarity

Each individual action is unambiguous and the slash-command and API sections are clearly grouped, though as a reference catalog it has no multi-step sequence or validation checkpoints (none are required for these non-destructive config actions).

4 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the full ~150-line API reference and platform table are inlined in SKILL.md; section headers provide structure, but bulk reference content that could live in a separate file remains inline.

3 / 5

Total

16

/

20

Passed

Description

48%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 is concise and names a clear niche, but it lacks concrete capability actions and any explicit trigger guidance for when to use the skill. Adding a 'Use when...' clause and a few specific actions would lift the weakest dimensions.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when configuring chunked response delivery, typing indicators, or per-platform message limits.'

List specific capabilities such as chunk size, inter-chunk delay, typing indicators, and per-platform limits instead of the generic 'configuration and real-time output'.

Include natural user phrases like 'streaming', 'typing indicators', and platform names (Telegram, Discord, Slack) to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase 'Response streaming configuration and real-time output' names the streaming domain but gives only minimal, generic actions ('configuration', 'output') rather than concrete capabilities like chunking or typing indicators.

2 / 5

Completeness

It clearly states what the skill does (streaming configuration) but provides no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

'Response streaming' and 'real-time output' are relevant keywords but the description omits common natural variations users would say such as 'typing indicators', 'chunked responses', or platform names.

3 / 5

Distinctiveness Conflict Risk

'Response streaming configuration' is a fairly specific niche with minimal overlap risk, though it could lightly overlap with a generic messaging skill.

4 / 5

Total

12

/

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

alsk1992/CloddsBot

Path

src/skills/bundled/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.