hwc-media-content
Handle media-heavy Hotwire features: image/video/audio uploads, previews, playback controls, progress tracking, and third-party media integrations (for example WaveSurfer, Swiper, Picture-in-Picture, Blurhash). Prefer this skill when the core problem is media rendering, playback state, or media library integration. Use hwc-realtime-streaming for server-pushed Turbo Stream updates, hwc-navigation-content for non-media pagination/tab/lazy-navigation flows, hwc-forms-validation for form validation and inline-edit behavior, hwc-ux-feedback for generic loading/transition patterns, and hwc-stimulus-fundamentals for Stimulus primitives not specific to media.
71
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 around media-heavy Hotwire features with specific actions, natural trigger terms, and explicit 'when to use' guidance. The disambiguation section listing five related skills and their respective domains is particularly strong, making it very easy for Claude to select the right skill from a large pool. The description is concise yet comprehensive, with no vague fluff or unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: image/video/audio uploads, previews, playback controls, progress tracking, and names specific third-party integrations (WaveSurfer, Swiper, Picture-in-Picture, Blurhash). | 3 / 3 |
Completeness | Clearly answers both 'what' (media uploads, previews, playback controls, progress tracking, third-party media integrations) and 'when' ('Prefer this skill when the core problem is media rendering, playback state, or media library integration'). Also explicitly delineates boundaries by naming related skills and when to use them instead. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'image', 'video', 'audio', 'uploads', 'previews', 'playback controls', 'progress tracking', plus specific library names like 'WaveSurfer', 'Swiper', 'Blurhash' that users would mention directly. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — not only defines its own clear niche (media-specific Hotwire features) but explicitly disambiguates from five related skills (hwc-realtime-streaming, hwc-navigation-content, hwc-forms-validation, hwc-ux-feedback, hwc-stimulus-fundamentals), greatly reducing conflict risk. | 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/orchestration skill that efficiently directs Claude to the right reference material based on the media task at hand. Its strengths are exceptional conciseness and progressive disclosure. Its main weakness is the lack of any inline executable code examples—all actionable implementation is deferred to reference files, and the workflow lacks explicit validation checkpoints for resource cleanup or state reconciliation.
Suggestions
Add at least one inline executable code snippet for a common pattern (e.g., blob URL preview with revocation in disconnect()) to improve actionability without relying entirely on reference files.
Add a validation/verification step to the core workflow, such as 'Verify in disconnect() that all blob URLs are revoked and all observers/timers are cleared' to strengthen the feedback loop for resource cleanup.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanation of what Stimulus or Turbo Frames are, no padding about media concepts. The guardrails and workflow steps are terse and assume Claude's competence with browser APIs and Hotwire conventions. | 3 / 3 |
Actionability | The skill provides a clear workflow and specific API names (URL.createObjectURL, PiP, IntersectionObserver, MediaSession) but lacks any executable code examples. All concrete implementation is deferred to reference files. The guidance is specific but not copy-paste ready on its own. | 2 / 3 |
Workflow Clarity | The 5-step core workflow is clearly sequenced and the guardrails add useful constraints, but there are no explicit validation checkpoints or feedback loops for operations like resource cleanup verification or reconciliation of persisted state on load. | 2 / 3 |
Progressive Disclosure | Excellent structure: concise overview with well-signaled, one-level-deep references to specific files organized by use case. The 'Load References Selectively' section with clear file paths and the INDEX.md fallback is a model of progressive disclosure. Neighbor skill escalation paths are clearly delineated. | 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.