zod

TypeScript-first schema validation and type inference. Use for validating API requests/responses, form data, env vars, configs, defining type-safe schemas with runtime validation, transforming data, generating JSON Schema for OpenAPI/AI, or encountering missing validation errors, type inference issues, validation error handling problems. Zero dependencies, compact core (~5kb gzipped; zod/mini ~1.9kb).

Quality

80%

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

Quality

Content

68%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 with executable examples and good progressive disclosure to real reference files, but it is token-heavy due to a duplicated full API quick-reference block and repetitive load-reference phrasings, and it lacks explicit validation checkpoints for any risky operations.

Suggestions

Remove or trim the standalone '## Quick Reference' code block (lines ~759-807) since every API it lists is already documented in the section-by-section catalog above it — this is the single biggest token saving.

Collapse the duplicated load-reference phrasings: each section currently has both a 'Load references/X.md for complete ...' header line and a '→ Load references/X.md for:' footer line; keep only one per section.

If any operation involves bulk or destructive validation (e.g. validating/transforming large inputs, env parsing on startup), add an explicit validate-then-handle checkpoint so workflow_clarity can exceed 3.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but padded in places: the large monolithic Quick Reference code block duplicates API listings already shown section-by-section, and the repeated 'Load references/X.md'/'→ Load ... for:' phrasings add tokens without earning their place.	3 / 5
Actionability	Abundant copy-paste-ready, executable TypeScript covering the common cases (basic parse/safeParse, coercion, discriminated unions, codecs, env validation, Express request validation, form schemas) with concrete method signatures.	5 / 5
Workflow Clarity	This is a reference catalog rather than a multi-step process, and the workflow guidance that exists (install → import → define schema → validate) is sequenced but lacks explicit validation checkpoints or feedback loops; no destructive/batch workflow is present to trigger the cap, so 3 is the ceiling rather than a penalty.	3 / 5
Progressive Disclosure	Clear overview structure with well-signaled, one-level-deep references to real bundle files (migration-guide, error-handling, advanced-patterns, type-inference, ecosystem-integrations, troubleshooting, best-practices all exist), plus a 'When to Load References' decision guide; a sizable API catalog and duplicated quick-reference remain inline, keeping it just below 5.	4 / 5
	Total	15 / 20 Passed

Description

92%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 precise, action-oriented, and covers what Zod does plus clear usage triggers with low conflict risk. It is only marginally held back by slightly incomplete synonym/file-extension coverage in its trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'validating API requests/responses, form data, env vars, configs', 'defining type-safe schemas with runtime validation, transforming data, generating JSON Schema for OpenAPI/AI' — giving comprehensive coverage of Zod's capabilities.	5 / 5
Completeness	Explicitly answers both what (schema validation, type inference, transforms, JSON Schema generation) and when via a 'Use for...' clause listing concrete trigger phrases including encountering specific error classes.	5 / 5
Trigger Term Quality	Strong natural terms ('API requests/responses, form data, env vars, configs', 'validation errors, type inference issues') but a few common synonyms or file-type hints (e.g. '.ts', 'schema validation library') are absent, keeping it just below a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (TypeScript-first Zod 4.x schema validation) with distinct triggers and an explicit reference to the related react-hook-form skill, minimizing conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (898 lines); consider splitting into references/ and linking	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/zod/skills/zod/SKILL.md
Commit: ad16332

Reviewed: 12 days 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.