CtrlK
BlogDocsLog inGet started
Tessl Logo

pleaseai/zod

TypeScript-first schema validation with static type inference - version-aware skill for Zod v3 and v4

80

Quality

100%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A well-structured, version-aware reference that leads with executable commands, sequences work with explicit validation, and offloads detail to real one-level-deep reference files. It is dense without being padded and assumes Claude's competence throughout.

DimensionReasoningScore

Conciseness

Lean and command-dense; assumes Claude's competence and avoids explaining what Zod is. Time-sensitive version pins are isolated to the deprecation-focused 'Critical' section and references/versions.md rather than scattered as prose.

3 / 3

Actionability

Provides copy-paste-ready bash (jq on package.json, 'ask src zod@4.3.6', rg symbol checks, node -e version detection) and concrete import-path tables rather than abstract direction.

3 / 3

Workflow Clarity

Sequenced guidance with validation checkpoints — 'Run typecheck after every change', 'Verify every API name... before generating code' — plus a 'When typecheck or runtime fails' feedback loop with grep-and-fallback recovery.

3 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep references (versions.md, schemas.md, parsing-and-errors.md), each described in the References section and linked inline; all referenced files exist in ./references/.

3 / 3

Total

12

/

12

Passed

Description

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.

A strong, third-person description that states concrete capabilities and pairs them with an explicit, enumerated 'Use when' trigger list plus a dedicated trigger-term block. It is specific, complete, and clearly distinct from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'build schemas, parsers, refinements, transforms, codecs, and error formatters' and 'migrate between Zod v3 and v4' — rather than vague language.

3 / 3

Completeness

Clearly answers 'what' ('Answer questions about the Zod schema validation library and help build...') and 'when' via an explicit 'Use when developers: (1)...(4)' clause.

3 / 3

Trigger Term Quality

The explicit 'Triggers on:' list covers the natural API tokens developers actually say (z.object, safeParse, ZodError, treeifyError, discriminatedUnion, zod/v4, etc.) with good breadth.

3 / 3

Distinctiveness Conflict Risk

Niche is tightly scoped to the Zod library with Zod-specific API triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents