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.
63
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/form-auto-save/SKILL.mdQuality
Discovery
57%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 identifies a clear and specific niche (debounced auto-form-submission) which gives it good distinctiveness, but it lacks an explicit 'Use when...' clause that would help Claude know when to select it. The trigger terms are decent but could include more natural user language variations and framework-specific keywords.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs forms that auto-submit on input change, debounced form submissions, or auto-save functionality.'
Include more natural trigger term variations such as 'auto-submit', 'onChange handler', 'throttle requests', 'form auto-save', and mention relevant frameworks like React or HTML forms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (form submission, debounce mechanism) and some actions (auto-save, preventing excessive server requests), but doesn't list multiple concrete implementation actions like specific code patterns, frameworks, or techniques. | 2 / 3 |
Completeness | The 'what' is reasonably covered (automatic form submission with debounce, auto-save experience), but there is no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'debounce', 'auto-save', 'form submission', 'rich text editors', but misses common user variations like 'auto-submit', 'throttle', 'onChange submit', 'form auto-save pattern', or specific framework names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of debounce mechanism + automatic form submission + auto-save is a fairly distinct niche that is unlikely to conflict with other skills. The specificity of the pattern (debounced form auto-submission) creates a clear trigger profile. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with complete, executable code examples for both implementation and testing. However, it is significantly verbose, explaining many concepts Claude already understands (passive listeners, what debouncing is, what turbo_permanent does) and including sections like 'When to Use' and 'Related Patterns' that add little value. The content would benefit from aggressive trimming and splitting the testing section into a separate reference file.
Suggestions
Remove explanatory text Claude already knows: 'When to Use' bullets, explanations of passive listeners, what turbo_permanent does, and the 'Related Patterns' section. Keep only the actionable implementation details.
Move the testing section (turbo_fetch controller, helper, and spec examples) into a separate TESTING.md file and reference it with a one-line link.
Trim 'Important Considerations' to just the key configuration values (debounce time default, event names) without explaining why they matter.
Condense 'Common Issues' into a brief troubleshooting checklist rather than expanded issue/solution blocks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. The 'When to Use' section, 'Important Considerations' explanations (e.g., explaining what passive listeners do, what turbo_permanent does), 'Common Issues' troubleshooting, and 'Related Patterns' sections all explain concepts Claude already knows. The skill could be cut by 50%+ without losing actionable content. | 1 / 3 |
Actionability | Provides fully executable, copy-paste ready code for the Stimulus controller, view integration (Slim templates), testing helper, and system specs. All code is concrete with specific file paths and complete implementations. | 3 / 3 |
Workflow Clarity | The implementation steps are numbered (1. Controller, 2. View Integration) and testing is well-sequenced, but there are no validation checkpoints. For a pattern involving automatic form submission (a potentially destructive operation), there's no explicit verification step to confirm the auto-save is working correctly during implementation. | 2 / 3 |
Progressive Disclosure | Content is structured with clear headers but is monolithic — the testing section alone is substantial and could be referenced as a separate file. The 'Common Issues' and 'Related Patterns' sections add bulk that could be externalized. No references to separate files for detailed content. | 2 / 3 |
Total | 8 / 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
097ad6b
- 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.