Name: form-builder
Rating: 49.6 (1 reviews)
Author: trackdubllc

Blog Docs Log inGet started

form-builder

Build accessible forms with React Hook Form + Zod

Quality

62%

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

The canonical home for this skill is form-builder in trackdubllc/Babel-Player-Alpha

Quality

Content

53%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 a clean, well-organized overview with good trigger guidance, but it functions as a pointer document whose targets are missing: the two example files it cites do not exist, and no inline code shows how to actually integrate React Hook Form with Zod. Either ship the example files or inline a minimal working form snippet.

Suggestions

Create the referenced examples/contact-form.tsx and examples/newsletter-signup.tsx (or remove the dead links), since the entire implementation guidance depends on them.

Inline a minimal executable snippet showing the RHF + Zod integration (zod schema, zodResolver, useForm, form component) so the skill is actionable without external files.

Add a short sequenced workflow (install -> define schema -> wire resolver -> build component -> handle submit) to make the build process explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padded prose, but the Stack section's parentheticals ("form state, minimal re-renders", "connects them") explain library roles Claude already knows, and the opening line "Build accessible, type-safe forms in React" duplicates the frontmatter description. These are minor instances that could be trimmed, matching the 4-anchor rather than the fully lean 5-anchor.	4 / 5
Actionability	The only executable artifact is the `npm install react-hook-form @hookform/resolvers zod` command; the body contains no form-building code and defers all implementation detail to examples/contact-form.tsx and examples/newsletter-signup.tsx, which do not exist in the bundle. Concrete guidance is present but incomplete with missing key details, matching the 3-anchor.	3 / 5
Workflow Clarity	The 'When to Use' section clearly defines activation triggers and the install step is concrete, but the actual build workflow (define Zod schema, wire zodResolver, build the form component, handle submission) is never sequenced in the body — it is only implied by the missing example files. Sequence is implicit with no checkpoints, matching the 3-anchor rather than the 2-anchor whose rough steps are at least listed.	3 / 5
Progressive Disclosure	The body's references are cleanly signaled one level deep with accurate one-line descriptions ('full implementation', 'minimal implementation'), but scoring against the actual bundle structure both referenced files (examples/contact-form.tsx, examples/newsletter-signup.tsx) are absent, so the references are dangling and navigation fails outright — worse than the 3-anchor's poorly signaled but functional references.	2 / 5
	Total	12 / 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.

A concise, technically specific description with a clear niche, but it answers only 'what' and not 'when'. Adding a trigger clause (e.g., 'Use when the user asks to create a form, add form validation, or handle form submission in React') would raise completeness and trigger-term quality simultaneously.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases such as 'Use when the user asks to create a form (contact, signup, login, checkout), add form validation, or handle form submission in React'.

Include natural synonyms users would say (form validation, signup form, login form) alongside the library names to improve trigger-term coverage.

Consider adding 1-2 more concrete actions (e.g., 'build type-safe schemas and wire validation') to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	"Build accessible forms" names one concrete action, anchored by the specific stack "React Hook Form + Zod". This matches the anchor for naming the domain with 1-2 concrete actions but not comprehensive coverage, unlike the 4-anchor which lists several distinct actions.	3 / 5
Completeness	The description has a clear 'what' ("Build accessible forms with React Hook Form + Zod") but no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"forms" is a natural keyword users would say, but the description omits common variations and phrases users actually use such as form validation, signup, login, or contact form. This sits at 'some relevant keywords but missing common variations', not the good-coverage 4-anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the exact stack ("React Hook Form + Zod") carves out a clear niche with only minor overlap risk against generic form- or validation-related skills. It falls short of the 5-anchor's minimal conflict risk because there is no explicit trigger phrasing to further disambiguate.	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: .github/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.