turbo-fetch
Implement dynamic form updates using Turbo Streams and Stimulus. Use when forms need to update fields based on user selections without full page reloads, such as cascading dropdowns, conditional fields, or dynamic option lists.
68
82%
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 a strong skill description that clearly defines a specific technical capability (dynamic form updates with Turbo Streams and Stimulus), provides explicit 'Use when' guidance with concrete trigger scenarios, and uses natural developer terminology. The description is concise, uses third person voice, and carves out a distinct niche that would be easy to differentiate from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'dynamic form updates using Turbo Streams and Stimulus', 'cascading dropdowns, conditional fields, or dynamic option lists'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Implement dynamic form updates using Turbo Streams and Stimulus') and when ('Use when forms need to update fields based on user selections without full page reloads') with explicit trigger guidance and concrete examples. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Turbo Streams', 'Stimulus', 'cascading dropdowns', 'conditional fields', 'dynamic option lists', 'form updates', 'user selections', 'without full page reloads'. Good coverage of terms a developer working in this space would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific technology stack (Turbo Streams + Stimulus) and the narrow use case (dynamic form updates with partial page updates). Unlikely to conflict with generic form or JavaScript skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides concrete, executable code for implementing the turbo fetch pattern across all necessary components. Its main weaknesses are redundancy (the codebase example section duplicates the implementation steps) and lack of explicit validation checkpoints in the workflow. The content could be tightened by removing duplicate examples and adding verification steps between implementation stages.
Suggestions
Remove or significantly condense the 'Examples from Codebase' section since it nearly duplicates the Implementation Steps — or merge them into a single walkthrough.
Add explicit validation checkpoints between steps, e.g., 'Verify route: `rails routes | grep turbo_fetch`' after Step 1, and 'Test in browser console that Stimulus controller connects' after Step 4.
Remove the 'Available turbo stream actions' list — Claude already knows these, and they're documented in Turbo's own docs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has some redundancy — the 'Examples from Codebase' section largely duplicates the Implementation Steps with nearly identical code. The 'Common Patterns' section restates what was already shown. The 'Available turbo stream actions' list is something Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code across all four components (routes, controller, Stimulus controller, views). Each step includes concrete code in the actual frameworks (Ruby, Slim, JavaScript) with specific file paths and naming conventions. | 3 / 3 |
Workflow Clarity | The five implementation steps are clearly sequenced and logically ordered. However, there are no explicit validation checkpoints — no step says 'verify the route exists before proceeding' or 'test the turbo stream response.' The troubleshooting section partially compensates but is reactive rather than preventive. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's monolithic — the examples, common patterns, and troubleshooting sections could be split into separate files. With no bundle files provided, there's no progressive disclosure to external references, and the single file is quite long. | 2 / 3 |
Total | 9 / 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
- RoleModel/rolemodel-skills
- Commit
72e8136
- 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.