Name: webiny-form-model
Rating: 66.4 (1 reviews)
Author: webiny

webiny-form-model

Building forms with the FormModel system — field types, renderers, layout, validation, conditional rules, computed fields, and dynamic zones. Use this skill when the developer needs to define form fields with the builder API, choose renderers, build layouts with tabs/rows/separators, add validation (Zod or imperative), use conditional visibility/disable rules, create computed fields, or work with object fields and templates (dynamic zones).

Quality

80%

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

Quality

Content

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

A highly actionable, dense API reference with excellent executable examples and minimal concept padding. Its main weakness is structure: nearly all reference material lives inline in SKILL.md with no progressive disclosure to separate files, and no explicit build/validate workflow.

Suggestions

Split the complete renderer reference table and the per-field-type catalog into separate reference files (e.g. RENDERERS.md, FIELD_TYPES.md) and have SKILL.md overview them with one-level-deep links.

Add a short numbered workflow (define fields → arrange layout → add validation → submit/validate) with an explicit validation checkpoint so the build process is sequenced rather than implicit.

Trim the redundant context-traversal examples (sibling, nested, deep-nesting, both) down to one representative example plus a brief note on the parent()/form patterns.

Dimension	Reasoning	Score
Conciseness	The body is dense API reference that assumes Claude's competence (no concept explanations for forms, Zod, or MobX), but the multiple near-identical context/cross-field traversal examples are minor redundancy that could be trimmed, keeping it just below a 5.	4 / 5
Actionability	Every section provides fully executable, copy-paste-ready TypeScript covering field types, renderers, layout, validation, computed fields, and context — matching the 5 anchor for copy-paste-ready examples across common cases.	5 / 5
Workflow Clarity	The implicit define→layout→validate sequence is conveyed through section ordering, but there are no explicit numbered steps, validation checkpoints, or feedback loops; this is reference-oriented rather than workflow-oriented, fitting the 3 anchor.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but ~770 lines of API reference (full renderer table, complete field-type catalog) are inlined in SKILL.md with no separate reference files and no bundle files present, so content that belongs in dedicated files is inline.	3 / 5
	Total	15 / 20 Passed

Description

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

A strong, specific description that clearly states what the skill does and when to use it with concrete trigger guidance. Its only weakness is trigger-term synonym coverage and minor overlap with a related Webiny skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "field types, renderers, layout, validation, conditional rules, computed fields, and dynamic zones" and "define form fields with the builder API, choose renderers, build layouts with tabs/rows/separators, add validation (Zod or imperative)" — giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	Explicitly answers both — the "what" ("Building forms with the FormModel system — ...") and an explicit "Use this skill when the developer needs to..." clause with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good natural-domain keywords a developer would say (forms, form fields, validation, layout, conditional rules, computed fields, dynamic zones, Zod), but it stops short of the synonym/file-extension comprehensiveness that defines a 5.	4 / 5
Distinctiveness Conflict Risk	The FormModel/builder-API niche is mostly distinct with specific triggers, but the broad "forms" term and the related webiny-page-settings-extensions skill create minor overlap risk with a closely related skill, fitting 4 over 5.	4 / 5
	Total	18 / 20 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
skill_md_line_count	SKILL.md is long (773 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/admin/form-model/SKILL.md
Commit: e1a2703

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.