streaming
Response streaming configuration and real-time output
65
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/streaming/SKILL.mdQuality
Discovery
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 brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient detail to distinguish it from other potentially similar skills. The description reads more like a topic label than actionable guidance for Claude.
Suggestions
Add specific concrete actions like 'Configure response streaming, handle chunked output, manage SSE connections, process partial responses'
Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks about streaming responses, real-time output, SSE, chunked responses, or live data feeds'
Include file extensions or API terms users might mention (e.g., 'Server-Sent Events', 'stream=true', 'chunked transfer encoding')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'configuration' and 'real-time output' without specifying concrete actions. It doesn't list what actions can be performed (e.g., enable streaming, configure chunk sizes, handle partial responses). | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (streaming configuration) and completely lacks any 'when' clause or explicit trigger guidance for when Claude should use this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('streaming', 'real-time output') that users might mention, but misses common variations like 'stream responses', 'live output', 'chunked responses', or 'SSE'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'streaming' is somewhat specific, 'real-time output' and 'configuration' are generic enough to potentially overlap with logging, monitoring, or other output-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API reference that excels in conciseness and actionability with clean, executable code examples. The main weaknesses are the lack of validation/verification guidance for confirming streaming configuration works correctly, and the monolithic structure that could benefit from splitting advanced topics into separate files for a 'complete' reference.
Suggestions
Add a verification section showing how to test that streaming is working correctly (e.g., a simple test command or expected console output)
Include error handling examples for common failure cases (network issues, platform rate limits)
Consider splitting platform-specific details into a separate PLATFORMS.md file with deeper coverage of edge cases
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting API reference material without unnecessary explanation. Every section serves a clear purpose with no padding or concepts Claude would already know. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples and concrete chat commands that are copy-paste ready. All configuration options are demonstrated with specific values and clear method signatures. | 3 / 3 |
Workflow Clarity | This is primarily an API reference rather than a multi-step workflow, but the best practices section lacks validation checkpoints. For a configuration skill, there's no guidance on verifying streaming is working correctly or troubleshooting common issues. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a helpful table, but everything is in one file. For a 'Complete API Reference', advanced topics like error handling, debugging, or platform-specific edge cases could be split into separate referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%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
2a8c94e
- 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.