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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with executable examples and a clear creation workflow. The main gaps are a missing verification checkpoint and some inlined content that could be split into reference files for a skill of this length.

Suggestions

Add an explicit verification step after registration (e.g., "Confirm the controller is listed in app/javascript/controllers/index.js before using it in HTML") to close the workflow_clarity validation gap.

Consider moving the Common Patterns and Key Concepts sections into a separate reference file and linking from the body, which would improve progressive_disclosure for a skill of this length.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with minimal padding; the only mild over-explanation is comments like "Called when controller is connected to DOM," so it sits at anchor 4 (efficient, minor trimming possible) rather than the fully lean anchor 5.	4 / 5
Actionability	It provides copy-paste-ready code, a specific registration command ("bin/rails stimulus:manifest:update"), and concrete examples covering the common cases (targets, values, actions, classes, common patterns), matching anchor 5.	5 / 5
Workflow Clarity	The create→register→use sequence is clear and flags registration as CRITICAL, but there is no explicit verification checkpoint (e.g., confirming the controller appears in index.js), placing it at anchor 4 with a minor validation gap; this is not a destructive/batch op so the cap-at-3 rule does not apply.	4 / 5
Progressive Disclosure	Content is well-organized into logical sections with no nested references and one-level "Related Skills" links; at ~130 lines it exceeds the simple-skill exception, and the inlined common-patterns section could be externalized, so it lands at anchor 4 (good structure, minor organization gaps) rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-constructed description that clearly states both its purpose and explicit trigger conditions with strong distinctiveness. It is slightly under-specified on concrete actions and lacks file-extension synonyms.

Suggestions

Add one or two more concrete actions (e.g., "wire up data attributes" or "connect events to methods") to lift specificity from 3 to 4.

Include the natural file/extension term (e.g., "_controller.js files") in the trigger clause for fuller trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Create and register Stimulus controllers" names the domain plus two concrete actions but nothing more, matching anchor 3 (1-2 concrete actions, not comprehensive); it lacks the several specific actions needed for a 4.	3 / 5
Completeness	It explicitly 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") with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	It includes natural phrases users say ("interactive JavaScript features," "client-side interactivity," "dynamic UI updates," "Stimulus controllers," "JavaScript behavior") for good coverage, but misses synonyms and file extensions like .js that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	"Stimulus controllers" is a clear, narrow niche with distinct triggers and minimal overlap with other skills, matching anchor 5 (clear niche, minimal conflict risk).	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: RoleModel/rolemodel-skills
Path: skills/stimulus-controllers/SKILL.md
Commit: 6d600e9

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.