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.

Quality

92%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

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, virtually eliminating conflict risk. The description is comprehensive yet concise, serving as a model for skill descriptions in a multi-skill environment.

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 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 to use instead for adjacent concerns.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'image', 'video', 'audio', 'uploads', 'previews', 'playback', 'media', plus specific library names like 'WaveSurfer', 'Swiper', 'Blurhash' that users would naturally mention.	3 / 3
Distinctiveness Conflict Risk	Exceptionally distinctive — not only defines a clear niche (media-heavy Hotwire features) but explicitly disambiguates from five related skills (hwc-realtime-streaming, hwc-navigation-content, hwc-forms-validation, hwc-ux-feedback, hwc-stimulus-fundamentals), making conflict very unlikely.	3 / 3
	Total	12 / 12 Passed

Implementation

85%

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 skill that efficiently routes Claude to the right reference material based on the media task at hand. Its strengths are exceptional organization, lean prose, and clear boundaries with neighboring skills. Its main weakness is the lack of any inline code examples—even a small representative Stimulus controller pattern or a blob URL cleanup snippet would make the skill more immediately actionable without needing to open a reference file.

Suggestions

Add 1-2 small inline code snippets for the most common patterns (e.g., a minimal Stimulus controller showing disconnect() cleanup of blob URLs or observer teardown) to improve actionability without bloating the file.

Consider adding a brief concrete example of the 'bridge third-party APIs through value callbacks and targets' pattern, as this is the most abstract guidance in the workflow and would benefit from a 3-5 line illustration.

Dimension	Reasoning	Score
Conciseness	Every line earns its place. No unnecessary explanations of what Stimulus, Turbo Frames, or browser APIs are. The content assumes Claude knows these technologies and focuses purely on decision-making guidance and resource pointers.	3 / 3
Actionability	The workflow and guardrails provide clear decision-making guidance, and the references point to concrete implementations. However, the skill itself contains no executable code examples—no Stimulus controller snippet, no blob URL revocation pattern, no disconnect() cleanup template. The actionability relies entirely on the referenced files.	2 / 3
Workflow Clarity	The 5-step core workflow is clearly sequenced and logically ordered (identify → state management → browser-native first → cleanup → persistence). The guardrails section adds validation-like constraints (revoke blob URLs, feature detection). For a routing/orchestration skill that delegates to reference files, this is appropriately clear.	3 / 3
Progressive Disclosure	Excellent progressive disclosure: concise overview with well-signaled one-level-deep references to specific files organized by use case. The 'Load References Selectively' instruction is explicit about opening only what's needed. Neighbor skill escalation paths are clearly delineated.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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: 12 days ago

Table of Contents

Discovery Implementation Validation

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.