form-auto-save

Automatic form submission after user input changes using a debounce mechanism to prevent excessive server requests. Creates a seamless auto-save experience for forms with rich text editors or multiple fields.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with complete, executable code and a clear implementation sequence, but it is somewhat verbose through repetition and inlines a large testing section that could be a separate reference. Adding an explicit auto-save failure feedback loop would raise workflow clarity.

Suggestions

Add an explicit validation/feedback checkpoint for auto-save failures (e.g., detect a failed request, surface an error, and retry) rather than only documenting failure in Common Issues.

Move the turbo-fetch controller, RSpec helper, and system spec into a dedicated testing reference file, keeping SKILL.md as a concise overview with a clearly signaled link.

Deduplicate the debounce-time and event-listener explanations that recur across the Overview, Implementation, and Important Considerations sections, and drop the questionable 'passive listeners for scroll performance' note.

Dimension	Reasoning	Score
Conciseness	The body is well sectioned with executable code, but the debounce rationale and event-listener details are repeated across Overview, Implementation, and Important Considerations, and 'passive listeners for better scroll performance' on change events is filler that could be trimmed.	2 / 3
Actionability	Provides fully executable, copy-paste-ready Stimulus controller code, Slim view snippets, a turbo-fetch controller, an RSpec helper, and a complete system spec with concrete file paths.	3 / 3
Workflow Clarity	Steps are sequenced (controller -> view -> testing), but auto-save is a server-persistence operation with no in-workflow validation checkpoint or validate->fix->retry feedback loop; failure handling lives only in a separate troubleshooting section, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist and the two trailing URLs are one-level references, but the ~210-line body keeps the entire testing controller, helper, and system spec inline rather than splitting them into a separate reference file.	2 / 3
	Total	9 / 12 Passed

Description

60%

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

The description concretely states what the skill does and names a clear niche, but omits an explicit 'Use when...' trigger clause and only partially covers the natural terms a user might say. Adding explicit trigger guidance and broader keyword coverage would lift the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when implementing auto-save for forms, rich text editors, or multi-field edit pages where users expect changes to persist automatically.'

Broaden natural keyword coverage to include common variations users say ('autosave', 'save form automatically', 'debounce form submission').

Tighten the distinctiveness by pairing the debounce mechanism with the specific trigger context so it cannot be confused with generic form-submission skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('form submission after user input changes', 'debounce mechanism to prevent excessive server requests', 'auto-save experience') plus concrete targets ('rich text editors or multiple fields'), matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers the 'what' but has no explicit 'Use when...' trigger clause; the 'when' is only implied via 'for forms with...', which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms like 'auto-save', 'form submission', and 'rich text editors', but misses common user variations such as 'autosave', 'save form', or 'debounce form'.	2 / 3
Distinctiveness Conflict Risk	The auto-save-via-debounce niche is somewhat specific and unlikely to conflict broadly, but lacks explicit distinct triggers that would firmly separate it from generic form-handling skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.