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.
66
79%
Does it follow best practices?
Impact
—
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 an explicit 'Use when' clause. Its main weaknesses are the somewhat generic capability description (only 'create and register') and the broad trigger terms like 'client-side interactivity' that could overlap with other frontend skills. Adding more Stimulus-specific actions and narrowing the broader triggers would improve it.
Suggestions
Add more specific Stimulus actions like 'define targets, values, actions, and outlets' to better convey the full scope of capabilities.
Narrow the broader triggers by tying them to the Stimulus/Rails ecosystem, e.g., 'Use when adding interactivity to Rails/Hotwire apps' to reduce conflict with generic JS framework skills.
| 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 good natural trigger terms: 'Stimulus controllers', 'JavaScript behavior', 'client-side interactivity', 'dynamic UI updates'. These cover the main ways a user would describe needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The Stimulus-specific terms provide some distinctiveness, but 'client-side interactivity' and 'dynamic UI updates' are broad enough to potentially conflict with general JavaScript, React, or other frontend 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, well-structured skill that provides clear, actionable guidance for creating Stimulus controllers. Its main strength is the clear three-step workflow with the critical registration step highlighted, plus executable code examples throughout. Its main weakness is that it includes substantial Stimulus library reference material (targets, values, actions, classes) inline that Claude likely already knows, which could be trimmed or moved to a separate reference file.
Suggestions
Move the Key Concepts section (Targets, Values, Actions, Classes) to a separate REFERENCE.md file and link to it, keeping SKILL.md focused on the project-specific workflow and conventions.
Trim explanatory comments in code examples (e.g., '// Called when controller is connected to DOM') since Claude already understands Stimulus lifecycle callbacks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content Claude would already know, such as comments like '// Called when controller is connected to DOM' and '// Your logic here'. The Key Concepts section is fairly comprehensive reference material that borders on documenting the Stimulus library itself rather than project-specific guidance. However, the naming conventions table and registration step are genuinely useful project-specific information. | 2 / 3 |
Actionability | The skill provides fully executable code examples throughout — controller creation, registration commands, HTML usage with Slim templates, and common patterns like form validation, toggle visibility, and AJAX updates. The `bin/rails stimulus:manifest:update` command and manual registration alternative are concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The three-step workflow (Create → Register → Use in HTML) is clearly sequenced with the critical registration step prominently marked. The troubleshooting section provides a clear diagnostic checklist. For this type of task (creating a controller), the workflow is appropriately structured with the validation/verification steps in troubleshooting. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom with clear links, which is good. However, the Key Concepts section (Targets, Values, Actions, Classes) and Common Patterns section are extensive inline content that could be split into a separate reference file, keeping the SKILL.md as a leaner overview. Without bundle files, all content is inlined in one document. | 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
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.