Build type-safe validated forms using React Hook Form v7 and Zod v4. Single schema works on client and server with full TypeScript inference via z.infer. Use when building forms, multi-step wizards, or fixing uncontrolled warnings, resolver errors, useFieldArray issues, performance problems with large forms.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill react-hook-form-zod98
Does it follow best practices?
Validation for skill structure
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 identifies the technology stack with versions, lists concrete capabilities and common pain points, and includes an explicit 'Use when...' clause with natural trigger terms developers would actually use. The specificity of mentioning particular error types and issues makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build type-safe validated forms', 'multi-step wizards', 'fixing uncontrolled warnings, resolver errors, useFieldArray issues, performance problems'. Mentions specific technologies (React Hook Form v7, Zod v4) and technical details (z.infer, TypeScript inference). | 3 / 3 |
Completeness | Clearly answers both what ('Build type-safe validated forms using React Hook Form v7 and Zod v4') AND when with explicit 'Use when...' clause covering multiple trigger scenarios (building forms, wizards, fixing specific errors). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'forms', 'multi-step wizards', 'uncontrolled warnings', 'resolver errors', 'useFieldArray issues', 'performance problems', 'large forms', 'React Hook Form', 'Zod'. These are terms developers naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting React Hook Form + Zod combination with version numbers. The specific error types (uncontrolled warnings, resolver errors, useFieldArray issues) create distinct triggers unlikely to conflict with generic form or React skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that maximizes information density while maintaining clarity. It provides comprehensive coverage of React Hook Form + Zod integration with executable code, explicit validation patterns, known issues with workarounds, and clear migration guidance for V8. The structure enables both quick reference and deep exploration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly efficient with no unnecessary explanations of basic concepts. Every section provides actionable information without padding, and code examples are minimal yet complete. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Each pattern includes complete TypeScript code with proper imports implied, specific API usage, and clear before/after comparisons for migrations. | 3 / 3 |
Workflow Clarity | Multi-step processes like form validation, server error handling, and multi-step forms have clear sequences. The Critical Rules section provides explicit validation checkpoints, and the Known Issues section prevents common failure modes. | 3 / 3 |
Progressive Disclosure | Well-organized with Quick Start for immediate use, then progressively deeper sections. References to bundled templates and external docs are clearly signaled at the end without nested indirection. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.