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

Quality

Content

71%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 exceptionally concise and well-structured for a simple skill, but it provides no inline form-building code and references example files that are missing from the bundle, weakening both actionability and progressive disclosure.

Suggestions

Add a minimal inline code example showing a React Hook Form + Zod form so the skill is actionable without external files.

Either include the referenced examples/contact-form.tsx and examples/newsletter-signup.tsx files in the bundle or remove the dead links.

Show a short build/validate sequence (define Zod schema, wire resolver, render fields, handle onSubmit) to make the workflow fully explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanation of concepts Claude already knows; each section (When to Use, Stack, Examples, Install) earns its tokens, matching the lean-and-efficient anchor.	5 / 5
Actionability	The install command is concrete and executable, but the core task of building a form has no inline executable code, and the two referenced example files do not exist in the bundle, leaving guidance incomplete.	3 / 5
Workflow Clarity	As a simple single-purpose skill it gives a clear install step, stack roles, and explicit triggers; this is not a destructive or batch operation so no validation cap applies, but the actual build sequence is only implied rather than shown.	4 / 5
Progressive Disclosure	Sections are well-organized, but the Examples section links to examples/contact-form.tsx and examples/newsletter-signup.tsx, and no examples/ directory exists in the bundle, so the one-level-deep references are broken and navigation fails.	3 / 5
	Total	15 / 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 specific, distinguishable stack, but it lacks an explicit "Use when" trigger clause and broader natural keyword coverage, leaving it at the midpoint across most dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to create, validate, or submit a form in React."

Broaden natural trigger terms to include validation, signup, login, and checkout so the description matches phrases users actually say.

Add one or two more concrete actions (e.g. validate form fields, handle submission) to raise specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	"Build accessible forms with React Hook Form + Zod" names the domain and one concrete action (build) plus a specific stack, but does not enumerate multiple distinct actions, so it matches the 1-2 concrete actions anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	It clearly states the what ("Build accessible forms with React Hook Form + Zod") but contains no "Use when..." trigger clause, so per the guideline a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	"forms" is a relevant natural keyword, but common variations and synonyms a user would actually say (validation, signup, login, contact form) are absent from the description, matching the some-keywords-missing-synonyms anchor.	3 / 5
Distinctiveness Conflict Risk	Naming a specific stack (React Hook Form + Zod) carves a clear niche with only minor overlap risk against other React form skills, fitting the mostly-distinct anchor above the somewhat-specific anchor at 3.	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: 7 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.