hwc-realtime-streaming
Implement real-time Hotwire behavior: Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list updates, and cross-tab state synchronization. Prefer this skill when the core problem is push-based updates or stream action orchestration. Use hwc-navigation-content for pull-based pagination/tab/lazy-navigation flows, hwc-forms-validation for form lifecycle and validation, hwc-media-content for media upload/playback behavior, hwc-ux-feedback for generic loading/progress/transitions, and hwc-stimulus-fundamentals for non-stream Stimulus fundamentals.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 an excellent skill description that clearly defines its scope (real-time push-based Hotwire/Turbo Streams behavior), provides explicit trigger guidance, and proactively disambiguates itself from related skills. The concrete capability list and explicit boundary-drawing with sibling skills make it highly effective for skill selection among a large pool of options.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list updates, and cross-tab state synchronization. These are clearly defined, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list updates, cross-tab state sync) and 'when' ('Prefer this skill when the core problem is push-based updates or stream action orchestration'). It also explicitly delineates boundaries by naming sibling skills and their domains. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'real-time', 'Hotwire', 'Turbo Streams', 'WebSocket', 'SSE', 'push-based updates', 'stream action', 'live list updates', 'cross-tab state synchronization'. These cover the natural vocabulary of developers working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — it explicitly names five sibling skills and explains when to use each one instead, creating very clear boundaries. The focus on push-based/real-time stream behavior is a well-defined niche unlikely to conflict with the named alternatives. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 orchestration/routing skill that excels at conciseness and progressive disclosure, effectively directing Claude to the right reference material and neighbor skills. Its main weakness is the lack of any concrete code examples or executable guidance in the body itself—it reads more as a decision framework than an actionable implementation guide. Adding even one or two small inline code snippets demonstrating common patterns would significantly improve actionability.
Suggestions
Add at least one concrete, executable code example inline—e.g., a minimal Turbo Stream broadcast snippet or a custom stream action registration—so the skill body itself is actionable without requiring a reference file.
Add an explicit validation checkpoint in the core workflow, such as 'After step 3, verify the stream action renders correctly in isolation before wiring transport' to create a feedback loop for error recovery.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what Turbo Streams or WebSockets are. The content assumes Claude's competence with Hotwire concepts and focuses purely on decision-making guidance and references. | 3 / 3 |
Actionability | The skill provides clear decision-making heuristics and guardrails, but lacks any concrete code examples, executable commands, or copy-paste-ready snippets. All concrete implementation details are deferred to reference files, making the skill itself more of a routing/decision document than an actionable guide. | 2 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence, and the guardrails mention validating failure modes and ordering. However, there are no explicit validation checkpoints, feedback loops, or error recovery steps within the workflow itself—verification is mentioned as a final step but not structured as a checkpoint gate. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, clearly signaled one-level-deep references to specific topics, an index file for the full catalog, and well-organized neighbor skill escalation paths. Each reference is labeled with its specific use case. | 3 / 3 |
Total | 10 / 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
- lucianghinda/superpowers-ruby
- Commit
cb03f92
- 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.