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 (2kb gzipped).
91
92%
Does it follow best practices?
Impact
88%
2.51xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its purpose (TypeScript schema validation), lists comprehensive concrete actions, and includes explicit trigger conditions via the 'Use for' clause. It uses proper third-person voice and includes both capability descriptions and problem scenarios that would trigger its use. The technical terms used are natural developer vocabulary.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific 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'. Very comprehensive coverage of capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('TypeScript-first schema validation and type inference') and when ('Use for validating API requests/responses, form data...' plus problem scenarios like 'missing validation errors, type inference issues'). The 'Use for' clause explicitly defines trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'API requests/responses', 'form data', 'env vars', 'configs', 'type-safe schemas', 'runtime validation', 'JSON Schema', 'OpenAPI', 'validation errors', 'type inference'. These are terms developers naturally use when discussing schema validation. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on TypeScript schema validation with distinct triggers like 'Zod-style' validation, 'type inference', 'runtime validation', and 'JSON Schema generation'. Unlikely to conflict with general TypeScript or generic validation skills due to specific focus on schema validation patterns. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent progressive disclosure and clear workflows. The main weaknesses are minor verbosity in the overview and installation sections, and some redundant explanatory text. The code examples are comprehensive and executable, and the reference system is well-organized with clear guidance on when to load each reference file.
Suggestions
Remove the duplicate 'bun add zod' commands in the installation section and trim the overview paragraph to be more concise
Consider removing explanatory phrases like 'Zod is a TypeScript-first validation library that enables developers to...' since Claude already knows what Zod is from the skill description
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the repeated 'bun add zod' installation commands and explanatory text that Claude would already know (e.g., 'Zod is a TypeScript-first validation library that enables developers to...'). The overview section could be leaner. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Every pattern includes concrete TypeScript code, from basic usage to complex patterns like environment variables, API validation, and form handling. | 3 / 3 |
Workflow Clarity | Clear workflows with explicit validation patterns. The parsing methods section clearly explains when to use each method, error handling shows explicit validation flows, and the 'When to Load References' section provides clear decision trees for navigating documentation. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to detailed documentation (migration-guide.md, error-handling.md, advanced-patterns.md, etc.). Each section has a 'Quick Reference' followed by clear pointers to load more detailed files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (803 lines); consider splitting into references/ and linking | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.