oRPC Disabling Output Validation

Disable output validation in oRPC procedures while generating OpenAPI specifications.

8|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ali-master/skills --skill orpc-disabling-output-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oRPC Disabling Output Validation
Source: https://github.com/ali-master/skills/tree/main/skills/orpc-disabling-output-validation
Command: npx skills add https://github.com/ali-master/skills --skill orpc-disabling-output-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows users to disable output validation in oRPC for improved performance while still generating OpenAPI specifications.

Core Features & Use Cases

  • Performance Improvement: By disabling output validation, users can increase the speed of their oRPC procedures.
  • OpenAPI Spec Generation: The Skill ensures that OpenAPI specifications are still generated without validation overhead.
  • Use Case: Ideal for scenarios where the primary goal is to generate OpenAPI specifications and the validation overhead is deemed unnecessary.

Quick Start

To disable output validation in your oRPC procedures, set initialOutputValidationIndex to NaN in your configuration.

Frequently Asked Questions about oRPC Disabling Output Validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I disable output validation in oRPC to improve performance?

To disable output validation in oRPC and improve performance, set `initialOutputValidationIndex` to `NaN` in your procedure configuration. This removes the validation overhead while still allowing OpenAPI specification generation.

Can I generate OpenAPI specifications in oRPC without validating outputs?

Yes, you can generate OpenAPI specifications without output validation by disabling the validation check. This ensures the spec is still produced, eliminating the performance overhead associated with validating response data.

Why does disabling output validation increase oRPC procedure speed?

Disabling output validation increases oRPC procedure speed by removing the computational overhead required to check response schemas against defined structures during runtime, allowing procedures to execute and return data faster.

When should I skip output validation in oRPC procedures?

You should skip output validation in oRPC procedures when your primary goal is generating OpenAPI specifications and you prioritize maximum performance over strictly validating response data at runtime.

What are the limitations of turning off output validation in oRPC?

The main limitation of turning off output validation in oRPC is the loss of strict runtime response checks. While it boosts performance and maintains OpenAPI spec generation, it risks returning unvalidated data structures to the client.