form-builder

Build accessible forms with React Hook Form + Zod

Quality

59%

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 ./.cursor/skills/form-builder/SKILL.md

Quality

Content

47%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 body is admirably lean and well-sectioned, but it contains almost no actionable content: one install command, a stack list, and links to example files that do not exist in the bundle. The skill needs at least one inline, copy-paste form example (schema + resolver + submit) and real example files to back its references.

Suggestions

Add a minimal inline example in the body: a Zod schema, the `zodResolver` wiring, and a small `useForm` field + submit handler — copy-paste ready for the common case.

Ship the referenced bundle files (`examples/contact-form.tsx`, `examples/newsletter-signup.tsx`) or remove the dead links — currently all substantive guidance points to nonexistent files.

Include a short ordered workflow (define schema → connect resolver → render accessible fields → handle submit) so the build process is sequenced rather than implied by the stack list.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean with zero padding: the Stack section's one-line notes ("form state, minimal re-renders", "connects them") justify choices rather than re-explain concepts Claude already knows. Matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place").	5 / 5
Actionability	The only executable guidance is `npm install react-hook-form @hookform/resolvers zod`; the core task — building a form — has no code, no Zod schema example, no resolver wiring, and no submission handling, matching anchor 2 ("Minimal concrete guidance; high-level hints but missing the specific steps to execute"). Not 3: there is no incomplete-but-concrete example of the actual skill task, only installation.	2 / 5
Workflow Clarity	There is no sequence for building a form (define schema → wire resolver → render fields → handle submit); the body offers only an install command and pointers to examples, matching anchor 2 ("Rough sequence present but many gaps; steps poorly defined"). Not 3 because not even a listed step sequence exists; not 1 because install-then-examples is a coherent, if skeletal, order.	2 / 5
Progressive Disclosure	The body offloads all substantive content to `examples/contact-form.tsx` and `examples/newsletter-signup.tsx`, but no `examples/` directory (nor any `references/`, `scripts/`, or `assets/`) exists in the bundle — the references dangle, echoing the bad example of content delegated to missing files. Matches anchor 2; not 3 because the sectioning is fine but the referenced payload is absent, leaving nothing to navigate to.	2 / 5
	Total	11 / 20 Passed

Description

53%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 is concise and names a distinct, specific niche (React Hook Form + Zod forms), but it is a single clause with no 'Use when...' trigger guidance and sparse natural-language keywords. Adding explicit trigger conditions and common user phrasings would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create or validate forms in React (contact, signup, login, checkout) or mentions React Hook Form, Zod, or form validation."

Enumerate 1-2 more concrete capabilities (e.g., "Define Zod schemas, wire resolvers, handle submission") to strengthen specificity beyond the single 'Build' verb.

Include natural synonyms and file/context cues ("React forms", "form validation", "signup/login forms") so the description matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	"Build accessible forms with React Hook Form + Zod" names the domain (accessible forms) and one concrete action plus the exact stack, matching anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"). It is not 4 because only a single action verb is given — validation, submission, and schema definition are not mentioned.	3 / 5
Completeness	The 'what' is clear ("Build accessible forms with React Hook Form + Zod") but there is no 'when' — no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is concrete, not vague.	3 / 5
Trigger Term Quality	"forms" is a natural keyword and "React Hook Form" / "Zod" are precise, but common user phrasings like "form validation", "signup form", "login form", or "React form" are absent — matching anchor 3 ("Some relevant keywords but missing common variations or synonyms"). It is not 4 because keyword coverage is thin, not just missing a few synonyms.	3 / 5
Distinctiveness Conflict Risk	"React Hook Form + Zod" pins a specific technical niche with minimal conflict risk, matching anchor 4 ("Mostly distinct; minor overlap risk with closely related skills"). Not 5 because the generic prefix "Build accessible forms" could still overlap with a general form-building or accessibility skill absent the library names.	4 / 5
	Total	13 / 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
relative_links	Relative link issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: trackdubllc/Babel-Player-Alpha
Path: .cursor/skills/form-builder/SKILL.md
Commit: 2237ca2

Reviewed: 13 hours 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.