iii-realtime-streams
Pushes live updates to connected WebSocket clients via streams. Use when building real-time dashboards, live feeds, or collaborative features.
70
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/iii-realtime-streams/SKILL.mdQuality
Discovery
75%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 is a competent description that clearly communicates both what the skill does and when to use it, with an explicit 'Use when' clause. Its main weaknesses are moderate specificity—it could enumerate more concrete actions—and trigger term coverage that misses some natural user phrasings like 'socket', 'push notifications', or 'real-time updates'.
Suggestions
Add more specific concrete actions such as 'broadcast messages to channels, manage client connections, handle subscriptions' to improve specificity.
Expand trigger terms to include common variations users might say, e.g., 'socket', 'push notifications', 'real-time updates', 'pub/sub', 'SSE'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WebSocket, streams) and a general action ('pushes live updates to connected WebSocket clients via streams'), but doesn't list multiple specific concrete actions like message broadcasting, connection management, or channel subscriptions. | 2 / 3 |
Completeness | Clearly answers both 'what' (pushes live updates to connected WebSocket clients via streams) and 'when' (Use when building real-time dashboards, live feeds, or collaborative features) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'WebSocket', 'real-time dashboards', 'live feeds', 'collaborative features', and 'streams', but misses common variations users might say such as 'push notifications', 'server-sent events', 'live updates', 'pub/sub', or 'socket'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of WebSocket, streams, and real-time push updates creates a clear niche that is unlikely to conflict with other skills. The specific technology (WebSocket) and use cases (dashboards, live feeds, collaborative features) are distinct enough. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of the realtime streams pattern with clear API surface documentation and good architectural context. Its main weaknesses are redundancy between sections (primitives table vs common patterns), lack of inline executable code examples, and missing workflow steps for end-to-end stream setup including error handling. The boilerplate 'When to Use' and 'Boundaries' sections at the end add little value.
Suggestions
Remove the 'Common Patterns' section or merge it with the 'iii Primitives Used' table to eliminate redundancy — they convey nearly identical information.
Add a minimal inline executable code example (e.g., a 5-10 line snippet showing stream::set followed by stream::send) rather than relying entirely on external reference files.
Add an explicit numbered workflow for setting up a stream end-to-end: configure engine → register worker → set stream items → send events → verify client receives, with a validation checkpoint.
Remove or condense the generic 'When to Use' and 'Boundaries' sections at the bottom — these are boilerplate that Claude doesn't need.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy — the 'Common Patterns' section largely repeats the 'iii Primitives Used' table, and the 'When to Use' and 'Boundaries' sections at the bottom contain generic boilerplate that doesn't add value. The architecture diagram and key concepts are lean, but overall it could be tightened. | 2 / 3 |
Actionability | The skill provides specific function signatures and payload structures which is helpful, but lacks inline executable code examples. It relies entirely on external reference files for working code. The trigger calls shown are descriptive patterns rather than copy-paste-ready implementations with context. | 2 / 3 |
Workflow Clarity | The architecture diagram shows the flow from function to WebSocket push, and the pattern boundaries help with decision-making. However, there's no explicit step-by-step workflow for setting up a stream end-to-end, no validation checkpoints, and no error handling guidance for WebSocket connection failures or stream operations. | 2 / 3 |
Progressive Disclosure | References to external files (realtime-streams.js/py/rs, iii-config.yaml, iii-browser-sdk skill) are clearly signaled and one level deep, which is good. However, no bundle files were provided, so the references cannot be verified as functional. The inline content also has some material (like the repeated primitive listings) that could be better organized. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- iii-hq/iii
- Commit
d51a06d
- 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.