output-error-zod-import

An incompatible schema error in Output SDK workflows usually occurs because Zod schemas are imported directly from the zod package instead of @outputai/core. Replacing those direct zod imports with @outputai/core ensures schema compatibility across step boundaries and resolves the runtime type mismatches.

To fix Zod import issues in TypeScript Output SDK workflows, locate all direct zod imports and replace them with @outputai/core. This skill automatically scans code paths defining inputSchema and outputSchema, adjusts dependent code, and ensures no direct zod imports remain to prevent mismatched schemas.

The correct way to import Zod schemas in Output SDK steps is by importing from @outputai/core rather than the standard zod library. Using @outputai/core ensures that all inputSchema and outputSchema definitions share the same schema instance, preventing type errors and runtime failures.

No, using standard zod imports with inputSchema and outputSchema definitions in Output workflows causes schema mismatches. You must import Zod schemas from @outputai/core to maintain compatibility and ensure that builds pass with tests across all defined steps.

The best way to locate and replace incorrect Zod imports across an Output SDK project is to run an automated scan that identifies all direct zod imports in schema definitions. This skill replaces them with @outputai/core imports and adjusts dependent code paths to verify builds pass.

If you don't update zod imports to @outputai/core in Output SDK workflows, you will encounter mismatched schemas and runtime errors at step boundaries. Direct zod imports create separate schema instances, leading to incompatible schema errors and failed builds during type validation.