stimulus-controllers
Create and register Stimulus controllers for interactive JavaScript features. Use when adding client-side interactivity, dynamic UI updates, or when the user mentions Stimulus controllers or JavaScript behavior.
83
79%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/stimulus-controllers/SKILL.mdQuality
Discovery
82%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 solid description that clearly communicates both what the skill does and when to use it, with good trigger terms for Stimulus-specific requests. Its main weaknesses are the somewhat generic capability description (only 'create and register') and the broad JavaScript trigger terms that could overlap with other JS framework skills. Adding more specific Stimulus actions and narrowing the non-Stimulus triggers would improve it.
Suggestions
Add more specific Stimulus capabilities like 'define targets, values, actions, and outlets' to improve specificity
Narrow the broader triggers to reduce conflict risk, e.g., 'Use when working with Hotwire/Stimulus, adding controller-based interactivity to server-rendered HTML, or when the user mentions Stimulus targets, values, or actions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Stimulus controllers) and two actions (create and register), but doesn't list more specific concrete actions like 'handle targets, values, actions, outlets' or other Stimulus-specific capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('Create and register Stimulus controllers for interactive JavaScript features') and when ('Use when adding client-side interactivity, dynamic UI updates, or when the user mentions Stimulus controllers or JavaScript behavior'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Stimulus controllers', 'JavaScript', 'client-side interactivity', 'dynamic UI updates', 'JavaScript behavior'. These cover common ways users would phrase requests for this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The Stimulus-specific terms provide some distinctiveness, but 'client-side interactivity', 'dynamic UI updates', and 'JavaScript behavior' are broad enough to potentially conflict with other JavaScript-related skills (e.g., vanilla JS, React, or other framework skills). | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
77%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 clear workflow steps and executable code examples throughout. Its main weakness is that it tries to serve as both a quick-start guide and a comprehensive Stimulus reference, making it longer than necessary. The Key Concepts and Common Patterns sections could be extracted to a separate reference file to improve conciseness and progressive disclosure.
Suggestions
Extract the Key Concepts and Common Patterns sections into a separate REFERENCE.md file, keeping only the essential creation workflow in SKILL.md
Remove inline comments that explain things Claude already knows (e.g., '// Called when controller is connected to DOM', '// Your logic here')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., comments like '// Called when controller is connected to DOM' that Claude already knows), and the Key Concepts section is fairly extensive reference material that could be linked out. However, it's mostly practical and not egregiously verbose. | 2 / 3 |
Actionability | The skill provides fully executable code examples throughout — controller creation, registration commands, HTML usage, common patterns, and testing. The code is copy-paste ready with real file paths and concrete commands like `bin/rails stimulus:manifest:update`. | 3 / 3 |
Workflow Clarity | The three-step workflow (Create → Register → Use in HTML) is clearly sequenced with numbered steps. The CRITICAL callout for registration is a strong validation checkpoint, and the troubleshooting section provides a clear error recovery checklist. | 3 / 3 |
Progressive Disclosure | The skill has good section organization and links to related skills at the bottom, but the Key Concepts and Common Patterns sections are quite lengthy inline content that could be split into a separate reference file. The main SKILL.md tries to be both a quick-start guide and a comprehensive reference. | 2 / 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
- 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.