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.
71
86%
Does it follow best practices?
Impact
—
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 specific capabilities around real-time Hotwire/Turbo Streams behavior, provides explicit trigger guidance for when to use it ('push-based updates or stream action orchestration'), and goes above and beyond by explicitly delineating boundaries with five related skills. The description uses proper third-person voice and includes rich, natural trigger terms that developers would use.
| 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 listing when to use other skills instead. | 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 differentiates itself from five related skills (hwc-navigation-content, hwc-forms-validation, hwc-media-content, hwc-ux-feedback, hwc-stimulus-fundamentals) with clear boundary guidance, making conflict with sibling skills very unlikely. | 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 routing and orchestration skill that excels at conciseness and progressive disclosure. Its main weakness is the lack of any concrete code examples or executable guidance in the body itself—it functions more as a decision tree and reference index than a hands-on implementation guide. The workflow is reasonable but would benefit from explicit validation/recovery steps given the inherently fragile nature of real-time streaming operations.
Suggestions
Add at least one concrete, executable code example in the body—e.g., a minimal Turbo Stream append over ActionCable or an inline stream tag snippet—so the skill is actionable without opening references.
Add explicit validation/feedback loop steps to the core workflow, such as how to verify stream delivery succeeded, how to handle reconnection, or how to test idempotency of stream actions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what Turbo Streams or WebSockets are. The skill assumes Claude knows Hotwire fundamentals and focuses purely on decision-making guidance and reference pointers. | 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. It relies entirely on references for concrete implementation details, making the body 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 step 5 mentions verifying ordering/idempotency/multi-tab behavior. However, there are no explicit validation checkpoints, feedback loops, or error recovery steps for what are inherently fragile real-time operations (out-of-order messages, reconnection, etc.). | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, selective reference loading with clear one-level-deep file paths, an INDEX.md pointer for the full catalog, and well-signaled neighbor skill escalation. The instruction to 'open only the file needed' is a strong progressive disclosure pattern. | 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
c037ce3
- 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.