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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

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

The body is a dense, executable quick-reference with strong actionability and decent conciseness, but the creation workflow lacks an inline verification step and the skill is monolithic with no progressive file structure and dead cross-skill links.

Suggestions

Add an explicit verification checkpoint to the creation workflow (e.g., '4. Verify: reload the page and confirm the controller is registered in app/javascript/controllers/index.js before proceeding').

Move the Key Concepts / Common Patterns API reference into a separate REFERENCE.md and link to it from a concise overview, so the SKILL.md stays a lean entry point.

Fix or remove the Related Skills links to ../frontend-patterns, ../turbo-fetch, and ../testing-patterns, which point to files that do not exist.

Dimension	Reasoning	Score
Conciseness	Lean reference of executable Stimulus API specifics (targets, values, actions, classes) that Claude cannot safely assume; it avoids explaining basic JS concepts, though the repeated `export default class extends Controller` boilerplate across pattern examples could be trimmed slightly.	3 / 3
Actionability	Provides copy-paste-ready controller templates, the exact registration command `bin/rails stimulus:manifest:update`, HTML/slim usage, and worked common patterns, satisfying the 'fully executable code/commands' anchor rather than the pseudocode level below.	3 / 3
Workflow Clarity	The 'Creating a New Controller' flow is clearly numbered (create, register, use) but has no inline verification checkpoint; validation is deferred to a reactive Troubleshooting section, matching the 'sequence present but checkpoints missing or implicit' anchor rather than the explicit-checkpoint level above.	2 / 3
Progressive Disclosure	A single well-sectioned 205-line file with no bundle files to offload the reference material into, and the only external links (Related Skills) point to non-existent paths; this fits the 'content that should be separate is inline' anchor rather than the well-signaled one-level-deep-references level above.	2 / 3
	Total	10 / 12 Passed

Description

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.

A strong, third-person description that states concrete capabilities and gives explicit 'Use when...' activation triggers with natural keywords. It closely matches the rubric's good examples and carries no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('Create and register Stimulus controllers') on a specific target, matching the 'lists multiple specific concrete actions' anchor rather than the single-domain 'names domain and some actions' level below.	3 / 3
Completeness	Explicitly answers both what ('Create and register Stimulus controllers for interactive JavaScript features') and when ('Use when adding client-side interactivity... or when the user mentions Stimulus controllers...'), matching the clear what-and-when-with-triggers anchor.	3 / 3
Trigger Term Quality	Covers natural terms users would say ('client-side interactivity', 'dynamic UI updates', 'Stimulus controllers', 'JavaScript behavior') with good variation, rather than the sparse 'some relevant keywords' anchor at 2.	3 / 3
Distinctiveness Conflict Risk	'Stimulus controllers' is a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor; it is not generic enough to overlap broadly as the 2-anchor example would.	3 / 3
	Total	12 / 12 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
Commit: f61959b

Reviewed: 10 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.