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 weakness is that the capability description could be more specific about what kinds of Stimulus controllers or patterns it supports, and the broad trigger terms like 'client-side interactivity' could cause conflicts with other frontend JavaScript skills.
Suggestions
Add more specific concrete actions like 'define targets, values, actions, and outlets' to better convey the full scope of Stimulus controller capabilities.
Narrow the broader trigger terms to reduce conflict risk—e.g., replace 'client-side interactivity' with 'Stimulus-based interactivity in Rails apps' or mention Hotwire/Turbo context.
| 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 terms users would naturally say when 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 other JavaScript/frontend skills (e.g., vanilla JS, Alpine.js, or general frontend 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 in a single file, making it longer than necessary. Some content like basic Stimulus API concepts (targets, values, actions) could be trimmed or moved to a separate reference file since Claude likely knows these already.
Suggestions
Move the Key Concepts and Common Patterns sections to a separate REFERENCE.md file, keeping SKILL.md focused on the create-register-use workflow
Remove explanatory comments like '// Called when controller is connected to DOM' that explain standard Stimulus lifecycle methods Claude already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content Claude would already know, such as explaining what `connect()` and `disconnect()` lifecycle methods do with comments, and the general concept of targets/values/actions which are standard Stimulus API. The common patterns section adds bulk that could be trimmed. | 2 / 3 |
Actionability | The skill provides fully executable code examples throughout — controller creation, registration commands, HTML usage with Slim syntax, and concrete patterns for form validation, toggle, and AJAX. The `bin/rails stimulus:manifest:update` command and manual registration alternative are specific 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 validation checklist for when things go wrong, serving as an effective feedback loop for debugging. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's quite long for a single file with no bundle support. The Key Concepts section (targets, values, actions, classes) and Common Patterns could be split into separate reference files. Related skills are referenced at the bottom, which is good, but the main file 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
4d83977
- 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.