CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zod-4

Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.

58

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./curated/zod-4/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A strong, code-dense reference: the breaking-changes section is well-executed and examples are largely executable. The main costs are token weight from Zod-3-identical basics that Claude already knows, and a monolithic single-file layout with no progressive disclosure.

Suggestions

Cut or compress sections that restate the unchanged Zod 3 API (basic primitives, optional/nullable, arrays) to keep only v4 deltas, and drop the trailing Keywords line.

Move secondary material (React Hook Form integration, extended pattern catalog) into a references/ file and link it from SKILL.md.

Fix the incomplete snippets: define onSubmit in the React Hook Form example and give userSchema.parse a concrete input.

Add a brief migration workflow (identify affected calls -> replace with v4 equivalents -> run typecheck/tests) so the skill guides a v3-to-v4 conversion rather than just listing patterns.

DimensionReasoningScore

Conciseness

Prose is lean and example-driven, but sizable sections ("Basic Schemas" with z.string()/z.boolean(), "Optional and Nullable", "Arrays and Records") restate the unchanged Zod 3 API Claude already knows, and the trailing "Keywords" line is padding. Mostly efficient, but it could be tightened to the v4 deltas.

3 / 5

Actionability

Nearly all TypeScript examples are executable and copy-paste ready (z.email({ error: ... }), z.record(z.string(), z.unknown()), safeParse handling), with minor gaps: the React Hook Form snippet submits to an undefined onSubmit and the parse example references an undeclared data variable.

4 / 5

Workflow Clarity

The decision-critical "Breaking Changes from Zod 3" section leads the file with a clear old/new contrast, and no destructive or batch operations require validation loops; however there is no guidance on sequencing a v3-to-v4 migration, and the >50-line simple-skill exception does not apply.

4 / 5

Progressive Disclosure

All ~205 lines are inlined in SKILL.md with no bundle files or references; the section headers give structure, but material like the React Hook Form integration and the full pattern catalog would naturally live in separate reference files.

3 / 5

Total

14

/

20

Passed

Description

68%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 has a clear niche and an explicit trigger, but it under-sells its capabilities: it names the domain without any concrete actions, leaving the reader to guess the coverage (schemas, errors, forms, migration). Adding 2-3 concrete verbs would lift specificity and completeness.

Suggestions

Enumerate concrete capabilities, e.g. "Build Zod 4 schemas, migrate Zod 3 code, configure error messages, integrate with React Hook Form".

Expand trigger terms to cover migration phrasing users would naturally say: "Use when migrating from Zod 3, writing Zod schemas, or hitting Zod validation errors".

State what the skill contains (breaking-change table, code patterns) so the 'what' is as explicit as the 'when'.

DimensionReasoningScore

Specificity

"Zod 4 schema validation patterns" names the domain clearly but lists zero concrete actions (no schema building, migrating v3 code, or error-handling verbs), matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

Both a 'what' ("Zod 4 schema validation patterns") and an explicit trigger clause ('Trigger: When using Zod for validation') are present, but the 'what' is terse and the 'when' could name more concrete trigger phrases.

4 / 5

Trigger Term Quality

"When using Zod for validation - breaking changes from v3" covers the natural terms (Zod, validation, breaking changes, v3/v4) a user would say, though variations like migration, upgrade, or TypeScript are missing.

4 / 5

Distinctiveness Conflict Risk

Zod is a specific library and the v3-to-v4 breaking-changes angle is a distinct niche, so it is clearly distinguishable from generic validation skills with minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Gentleman-Programming/Gentleman-Skills

Path

curated/zod-4/SKILL.md

Reviewed

Table of Contents

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.