Download for MacApple silicon, macOS 14+
Skill

output-error-zod-import

@growthxai Updated 2026-10-22

Fix Zod schema import issues in Output SDK workflows. Use when seeing "incompatible schema" errors, type errors at step boundaries, schema validation failures, or when schemas don't match between steps.

agentsaiai-agentsai-sdkclaudeclaude-codejavascriptllm

Install

With your agent

Install OMGSkills skill "growthxai/output:coding_assistants/claude/plugins/outputai/skills/output-error-zod-import" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/growthxai/output /tmp/output && ln -s /tmp/output/coding_assistants/claude/plugins/outputai/skills/output-error-zod-import ~/.claude/skills/output-error-zod-import

From README

Fix Zod Import Source Issues Overview 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. When to Use This Skill You're seeing: "incompatible schema" errors Type errors at step boundaries Schema validation failures when passing data between steps Errors mentioning Zod types not matching "Expected ZodObject but received..." errors Root Cause 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.