zod-validation-expert

Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.

Quality

70%

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 ./skills/zod-validation-expert/SKILL.md

Quality

Content

71%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, highly actionable Zod reference skill with excellent executable code examples covering the most important use cases and integrations. Its main weaknesses are moderate verbosity (unnecessary explanatory prose and a role-play preamble that Claude doesn't need) and a monolithic structure that would benefit from splitting integration patterns into separate referenced files. The troubleshooting section is a nice practical touch.

Suggestions

Remove the 'Why Zod?' explanatory section and the role-play preamble ('You are a production-grade Zod expert') — Claude already understands these concepts and the frontmatter handles skill identity.

Split integration patterns (React Hook Form, Next.js, env vars) into separate bundle files (e.g., INTEGRATIONS.md) and reference them from the main skill to improve progressive disclosure.

Trim the 'When to Use This Skill' section to 2-3 bullet points or remove it entirely — the skill's purpose is clear from the content itself.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanations Claude already knows (e.g., 'Why Zod?' section explaining the concept of runtime vs static validation, 'Zod eliminates the duplication...', explaining what safeParse returns). The 'When to Use This Skill' section is also somewhat redundant. However, the code examples themselves are lean and well-chosen. The role-play preamble ('You are a production-grade Zod expert') adds no value.	3 / 5
Actionability	Every section provides fully executable, copy-paste ready TypeScript code covering primitives, objects, parsing, refinements, transformations, and all major integrations (React Hook Form, Next.js Server Actions, env vars). The examples are complete and cover common real-world use cases with proper imports.	5 / 5
Workflow Clarity	The skill is primarily a reference/pattern skill rather than a multi-step workflow, but the Next.js Server Actions example demonstrates a clear validation workflow with error handling and success paths. The parse vs safeParse section clearly shows the preferred pattern with control flow. Minor gap: no explicit workflow for setting up a project with Zod from scratch or a validation pipeline checklist.	4 / 5
Progressive Disclosure	The content is a single monolithic file at ~200+ lines with no references to external files. While the sections are well-organized with clear headers, the integration patterns (React Hook Form, Next.js, env vars) and troubleshooting could reasonably be split into separate files. For a skill of this length, some progressive disclosure via bundle files would improve navigability.	3 / 5
	Total	15 / 20 Passed

Description

70%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 does a good job identifying the specific library (Zod), its core capabilities, and key integration points, making it highly distinctive. However, it lacks an explicit 'Use when...' clause, which weakens its completeness for skill selection. Adding trigger guidance and a few more natural user phrases would significantly improve it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Zod schemas, TypeScript validation, or integrating schema validation with React Hook Form, Next.js, or tRPC.'

Include additional natural trigger terms like 'validate input', 'form validation', 'type-safe', or '.zod' to capture more user query variations.

Dimension	Reasoning	Score
Specificity	Lists several specific actions (parsing, custom errors, refinements, type inference) and names concrete integrations (React Hook Form, Next.js, tRPC). Minor gaps in that it doesn't enumerate all possible Zod operations like transforms, coercion, or discriminated unions.	4 / 5
Completeness	The 'what' is clearly stated with specific capabilities and integrations, but there is no explicit 'when' clause (e.g., 'Use when...'). The absence of a 'when' trigger guidance caps this at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes strong natural keywords: 'Zod', 'schema validation', 'TypeScript', 'parsing', 'React Hook Form', 'Next.js', 'tRPC'. Missing some natural user phrases like 'validate input', 'form validation', 'schema definition', or 'type-safe validation'.	4 / 5
Distinctiveness Conflict Risk	Zod is a very specific library, and the description names it explicitly along with its unique integration points (tRPC, React Hook Form). This creates a clear niche with minimal conflict risk against other validation or TypeScript skills.	5 / 5
	Total	16 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/zod-validation-expert/SKILL.md
Commit: 900c504

Reviewed: 2 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.