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.
86
82%
Does it follow best practices?
Impact
Pending
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 identifies a specific technology combination (Turbo Streams and Stimulus) for a well-defined use case (dynamic form updates). It includes an explicit 'Use when' clause with concrete examples of triggering scenarios, and uses appropriate third-person voice throughout. The natural trigger terms cover both the technology stack and the user-facing problem domain effectively.
| 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 Rails/Hotwire developer would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific technology stack (Turbo Streams + Stimulus) combined with the specific use case (dynamic form 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 with concrete, executable code examples covering all four components of the turbo fetch pattern. Its main weaknesses are redundancy (the codebase example section duplicates the implementation steps) and lack of validation checkpoints in the workflow. The content would benefit from trimming duplicate examples and either integrating verification steps into the workflow or splitting supplementary content into referenced files.
Suggestions
Remove or significantly condense the 'Examples from Codebase' section since it duplicates the implementation steps—or replace the implementation steps with the concrete example and keep only one version.
Add validation checkpoints to the workflow, e.g., 'After step 1, verify route: `rails routes | grep turbo_fetch`' and 'After step 4, test in browser that the Stimulus action fires before proceeding.'
Move the Common Patterns, Tips, and Troubleshooting sections into a separate reference file (e.g., TURBO_FETCH_REFERENCE.md) and link to it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some redundancy—the 'Examples from Codebase' section largely duplicates the implementation steps above it, and the 'Common Patterns' section restates what was already shown. The turbo stream actions list and some explanatory comments could be trimmed. | 2 / 3 |
Actionability | Provides fully executable code for every component: routes, controller, Stimulus JS, Slim views, and turbo stream templates. All examples are copy-paste ready with specific file paths and concrete syntax. | 3 / 3 |
Workflow Clarity | The 5 implementation steps are clearly sequenced and logically ordered. However, there are no validation checkpoints—no step to verify the route exists before proceeding, no mention of testing the turbo stream response, and the troubleshooting section is separate rather than integrated as feedback loops within the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's monolithic—the examples, common patterns, tips, and troubleshooting sections could be split into separate reference files. No external file references are used despite the content being 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
097ad6b
- 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.