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

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/form-auto-save/SKILL.md

Quality

Content

75%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.

The content is highly actionable with complete, executable examples and a clear implementation-to-testing sequence. Its main weakness is repetition across sections that inflates length without adding information.

Suggestions

Remove the Overview restatement of the description and consolidate the debounce/event-listener explanations into one section to cut repetition between 'Key Features', 'Important Considerations', and 'Common Issues'.

Move the testing appendix (turbo-fetch controller, helper, system spec) into a separate references file (e.g. TESTING.md) and link to it from the body to improve progressive disclosure.

Add an explicit validation checkpoint in the implementation flow (e.g. 'verify the controller is attached and a request fires') to push workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but repeats itself: the Overview restates the frontmatter description, and debounce/event-listener details appear in the controller code, 'Important Considerations', and 'Common Issues'; these could be tightened.	3 / 5
Actionability	Provides copy-paste-ready, fully executable code for the Stimulus controller, the turbo-fetch controller, the RSpec helper, Slim view integration, and complete system spec examples covering the common cases.	5 / 5
Workflow Clarity	The implementation is clearly sequenced (1. Stimulus Controller, 2. View Integration) with a dedicated Testing section that serves as verification; minor validation gaps keep it just below 5, and no destructive/batch cap applies.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with external references (Stimulus/Turbo URLs) signaled at the end; however all code and the testing appendix are inlined in a ~200-line single file rather than split into reference files, so it is not a 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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.

The description clearly communicates what the skill does with concrete, mostly natural language, but omits an explicit 'Use when...' trigger clause, which caps completeness. It is distinct and reasonably specific.

Suggestions

Add an explicit trigger clause such as 'Use when building forms that should save automatically as users edit, especially rich text editors or multi-field edit pages.'

Include more natural user phrasings like 'auto-save' / 'save form automatically' / 'prevent lost changes' to broaden trigger coverage.

Trim the benefit phrasing ('seamless auto-save experience') in favor of one more concrete action to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Automatic form submission after user input changes', 'debounce mechanism to prevent excessive server requests', and 'auto-save experience for forms with rich text editors or multiple fields'; minor coverage gaps keep it below 5.	4 / 5
Completeness	The 'what' is clear but there is no explicit 'Use when...' trigger clause; the guideline caps completeness at 3 when explicit trigger guidance is missing, and the 'when' is only weakly implied by 'forms with rich text editors or multiple fields'.	3 / 5
Trigger Term Quality	Contains natural terms a user would say ('form submission', 'auto-save', 'forms', 'rich text editors', 'multiple fields'), but misses common variations like 'save form automatically' or 'prevent losing changes'.	4 / 5
Distinctiveness Conflict Risk	It targets a clear niche (debounced form auto-save) with distinct triggers and minimal conflict risk, though the broad 'forms' framing has minor overlap with general form-handling skills.	4 / 5
	Total	15 / 20 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
Path: skills/form-auto-save/SKILL.md
Commit: 6d600e9

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