Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ledgerhq/zod-schemas
Zod schema validation patterns for API types
Passed 22 of 23 test cases with the skill, and 16 of 23 without it.
and 7 more in the full report
6 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the prescribed top-to-bottom sequence of code sections inside state-manager/types.ts?
| Checked | Without skill | With skill |
|---|---|---|
| Places tag enums first followed by schemas then inferred types then query param interfaces and schema exports at the bottom | Missed | Passed |
The instructions your model reads when the skill loads.
Define types in state-manager/types.ts using Zod schemas for runtime validation.
// ✅ GOOD - state-manager/types.ts
import { z } from "zod";
// 1. Define tag types as enum
export enum MyDataTags {
Items = "Items",
Item = "Item",
}
// 2. Define Zod schemas with validation rules
const ItemSchema = z.object({
id: z.string().uuid(),
name: z.string().min(1),
value: z.number().min(0),
status: z.enum(["active", "inactive"]),
createdAt: z.string().datetime(),
});
const ItemResponseSchema = z.object({
data: ItemSchema,
meta: z.object({
timestamp: z.string(),
version: z.string(),
}),
});
const ItemListResponseSchema = z.object({
items: z.array(ItemSchema),
pagination: z.object({
test cases passed, vs 16 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.