CtrlK
BlogDocsLog inGet started
Tessl Logo

hwc-navigation-content

Build Hotwire navigation and content-discovery flows: Turbo Frame pagination, tabbed navigation, lazy loading, faceted filtering/search, cache lifecycle, scroll restoration, and visit/render control. Prefer this skill when the core problem is request/response navigation state and browser history behavior. Use hwc-forms-validation for form validation and inline edit flows, hwc-realtime-streaming for WebSocket/Turbo Stream push updates, hwc-media-content for image/video/audio features, hwc-ux-feedback for generic loading/progress/transition polish, and hwc-stimulus-fundamentals for Stimulus APIs not centered on navigation.

71

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 navigation skill that excels at conciseness and progressive disclosure, serving as an effective routing document to detailed references. Its main weakness is the lack of any concrete code examples or executable snippets in the body itself—all actionable detail is deferred to reference files. The workflow is clear in sequence but could benefit from more specific validation guidance and error recovery steps.

Suggestions

Add at least one concrete code example (e.g., a minimal Turbo Frame tab navigation pattern with data-turbo-action and frame src) to make the skill actionable without requiring reference file access.

Expand step 5 of the workflow with specific validation techniques (e.g., 'navigate forward, press back, verify URL and active state match; refresh and confirm no stale UI artifacts') and what to do when validation fails.

DimensionReasoningScore

Conciseness

Every line earns its place. No unnecessary explanations of what Turbo Drive or Turbo Frames are. Assumes Claude knows the framework and focuses purely on decision-making workflow, guardrails, and reference pointers.

3 / 3

Actionability

The workflow and guardrails provide clear conceptual guidance (classify navigation mode, decide URL ownership, clean cache snapshots), but there are no concrete code examples, executable snippets, or specific HTML/Stimulus patterns. All executable detail is deferred to reference files which were not provided for evaluation.

2 / 3

Workflow Clarity

The 5-step core workflow is clearly sequenced and includes a validation step (step 5: 'Validate behavior across forward/back navigation and refresh paths'). However, there are no explicit feedback loops for error recovery, and the validation step is vague—it doesn't specify how to validate or what to do if validation fails.

2 / 3

Progressive Disclosure

Excellent progressive disclosure structure: concise overview with guardrails at the top, clearly signaled one-level-deep references to specific topic files, an INDEX.md for full catalog, and well-organized neighbor skill escalation paths. References are topically labeled and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

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 lists specific concrete capabilities, includes natural trigger terms developers would use, explicitly states when to use it, and proactively disambiguates from related skills. The boundary-drawing with sibling skills is particularly strong and reduces conflict risk significantly. The description uses proper third-person voice throughout.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: Turbo Frame pagination, tabbed navigation, lazy loading, faceted filtering/search, cache lifecycle, scroll restoration, and visit/render control. These are all clearly defined, concrete capabilities.

3 / 3

Completeness

Clearly answers both 'what' (Turbo Frame pagination, tabbed navigation, lazy loading, etc.) and 'when' ('Prefer this skill when the core problem is request/response navigation state and browser history behavior'). It also explicitly delineates boundaries by naming related skills and their domains.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'pagination', 'tabbed navigation', 'lazy loading', 'faceted filtering', 'search', 'scroll restoration', 'browser history', 'Turbo Frame', 'Hotwire'. These cover the terms developers naturally use when dealing with navigation concerns.

3 / 3

Distinctiveness Conflict Risk

Exceptionally distinctive — it explicitly names five sibling skills and clarifies the boundary with each (forms, realtime, media, UX feedback, Stimulus fundamentals). The trigger condition ('request/response navigation state and browser history behavior') carves out a clear niche unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
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.