Install any skill in seconds. Free to start, no credit card required.
Get Started Free →growthxai/output-error-zod-import
Fix Zod schema import issues in Output SDK workflows.
Passed 23 of 23 test cases with the skill, and 13 of 23 without it.
and 9 more in the full report
10 fixed13 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the exact npm script name defined in the standard Output SDK project template that is used to compile the worker before testing a workflow run?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies output:worker:build | Missed | Passed |
The instructions your model reads when the skill loads.
This skill helps diagnose and fix a common issue where Zod schemas are imported from the wrong source. Output SDK requires schemas to be imported from @outputai/core, not directly from zod.
You're seeing:
The issue occurs when you import z from zod instead of @outputai/core. While both provide Zod schemas, they create different schema instances that aren't compatible with each other within the Output SDK context.
Why this matters: Output SDK uses a specific version of Zod internally for serialization and validation. When you use a different Zod instance, the schemas are technically different objects even if they define the same shape.
Error: Incompatible schema types
Error: Schema validation failed: expected compatible Zod instance
TypeError: Cannot read property 'parse' of undefined
// WRONG: Importing from 'zod' directly
import { z } from 'zod';
const inputSchema = z.object( {
name: z.string()
} );
test cases passed, vs 13 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.