forms-and-validation
Guide Claude on building forms with Binder and robust validation in Vaadin 25 Flow. This skill should be used when the user asks to "create a form", "bind fields", "validate input", "use Binder", "use BeanValidationBinder", "add validation", "convert field values", "handle form submission", "cross-field validation", or needs help with field binding, converters, required fields, custom validators, or form error handling in Vaadin Flow.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that excels across all dimensions. It clearly defines its scope (Vaadin 25 Flow form building with Binder), provides extensive natural trigger terms that users would actually say, and explicitly states when the skill should be used. The framework-specific terminology ensures high distinctiveness with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: building forms with Binder, robust validation, binding fields, converting field values, handling form submission, cross-field validation, custom validators, and form error handling. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (building forms with Binder and robust validation in Vaadin 25 Flow) and 'when' (explicit 'This skill should be used when...' clause with extensive trigger terms and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'create a form', 'bind fields', 'validate input', 'use Binder', 'use BeanValidationBinder', 'add validation', 'convert field values', 'handle form submission', 'cross-field validation', plus additional terms like 'converters', 'required fields', 'custom validators', and 'form error handling'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Vaadin 25 Flow forms and Binder specifically. The combination of framework-specific terms (Vaadin Flow, Binder, BeanValidationBinder) and domain-specific actions makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, highly actionable skill with excellent executable code examples covering Vaadin Binder fundamentals, binding, converters, and multi-layer validation. Its main weaknesses are moderate verbosity (some explanations Claude doesn't need, restated best practices) and the lack of a clear end-to-end form-building workflow with explicit validation checkpoints. The progressive disclosure structure is reasonable but the referenced file is missing from the bundle.
Suggestions
Add a concise end-to-end workflow section (e.g., numbered steps: create fields → configure bindings → set up error display → handle save button → validate → write bean → handle errors) with explicit validation checkpoints.
Trim the best practices section to only include non-obvious guidance not already demonstrated in the code examples above it.
Provide the referenced `references/form-patterns.md` file in the bundle, or remove the reference if it doesn't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary explanations Claude would already know (e.g., explaining what HasValue components are, explaining that converters 'implicitly validate'). The best practices section restates guidance already covered in the body. Some tightening is possible. | 2 / 3 |
Actionability | Excellent actionable content throughout — fully executable Java code examples for every concept (buffered/write-through modes, explicit binding, converters, all validation layers, form layout). Code is copy-paste ready with realistic patterns and specific class names. | 3 / 3 |
Workflow Clarity | The two modes of operation are clearly distinguished with guidance on when to use each. However, there's no explicit end-to-end workflow showing the complete form creation sequence (create fields → bind → validate → handle submission → display errors). The validation triggering section lists options but doesn't sequence them into a clear workflow with checkpoints. | 2 / 3 |
Progressive Disclosure | The skill references `references/form-patterns.md` at the end and mentions MCP tools at the top, which is good structure. However, the body itself is quite long (~180 lines) and could benefit from splitting validation layers or converter patterns into separate reference files. The referenced file doesn't exist in the bundle, making it impossible to verify the reference is useful. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- vaadin/claude-plugin
- Commit
e47fdfe
- 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.