Name: zod-validation-expert
Rating: 58.4 (1 reviews)
Author: administrakt0r

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

67%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/zod-validation-expert/SKILL.md

The canonical home for this skill is zod-validation-expert in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%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 highly actionable, packed with executable examples across Zod's core and integration surfaces, and well-organized into sections. It loses points for verbosity in explanatory prose, the absence of any multi-step workflow with checkpoints, and lack of progressive disclosure into separate reference files.

Suggestions

Trim the introductory and 'Why Zod?' prose to assume Claude's existing knowledge of TypeScript and validation libraries.

Move the integration-pattern details (React Hook Form, Next.js, tRPC) into separate reference files linked from a concise overview to improve progressive disclosure.

Add a short canonical workflow (define schema → safeParse → branch on success/error) with an explicit validation checkpoint to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy and largely tight, but the intro paragraph and 'Why Zod?' section restate concepts Claude already knows ('Zod eliminates the duplication of writing a TypeScript interface and a runtime validation schema'), and inline comments pad examples — matching 'mostly efficient but includes some unnecessary explanation', not the lean 5.	3 / 5
Actionability	Abundant copy-paste-ready, executable TypeScript examples cover the common cases — primitives, coercion, object inference, safeParse, custom errors, refinements, transformations, and RHF/Next.js/env integrations — fully satisfying 'specific examples cover the common cases'.	5 / 5
Workflow Clarity	This is a reference/knowledge skill with no multi-step destructive workflow; sections are well-organized but lack any explicit sequence with validation checkpoints, fitting the 'sequence present but checkpoints missing or implicit' anchor rather than 4.	3 / 5
Progressive Disclosure	No bundle files exist and all content (~260 lines) is inlined in SKILL.md; sections are clearly headed, but substantial API-reference-style material that could live in separate reference files is inline, matching 'some structure but content that should be separate is inline' rather than a well-split 4 or 5.	3 / 5
	Total	14 / 20 Passed

Description

70%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 specific and distinctive, clearly scoping a Zod validation niche with concrete capabilities and natural trigger terms. Its main weakness is the absence of an explicit 'when to use' clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when validating API/form inputs with Zod, or when integrating Zod with React Hook Form, Next.js Server Actions, or tRPC.'

Mention coercion/transformations in the capability list to close the coverage gap relative to the body content.

Dimension	Reasoning	Score
Specificity	Names the Zod domain and lists several concrete actions — 'parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC' — with only minor coverage gaps (e.g., transformations/coercion omitted), fitting the 'several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	Provides a clear 'what' ('Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference...') but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms developers actually say — 'Zod', 'schema validation', 'React Hook Form', 'Next.js', 'tRPC' — giving good keyword coverage, though a few natural synonyms (e.g., 'form validation', file extensions) are missing, so not a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Zod with named integrations (React Hook Form, Next.js, tRPC) — yielding distinct triggers and minimal conflict risk with other validation skills.	5 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

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

Reviewed: 1 hour 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.