validate-spec

Validate OpenAPI documents and report errors with JSON path references.

5|5|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/erraggy/oastools --skill validate-spec-erraggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-spec
Source: https://github.com/erraggy/oastools/tree/main/plugin/skills/validate-spec
Command: npx skills add https://github.com/erraggy/oastools --skill validate-spec-erraggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenAPI specs often contain subtle errors that break tooling, generate incorrect client code, or fail validation. This skill provides a guided workflow to validate, explain, and suggest or apply fixes for OpenAPI documents.

Core Features & Use Cases

  • Validate OpenAPI documents (2.0–3.2) and detect structural, semantic, and schema errors.
  • Explain each error with a plain-language rationale and point to the exact location in the document.
  • Propose deterministic fixes or auto-fix options and re-validate the corrected spec.

Quick Start

Use the validate-spec tool on a user-provided spec file to generate a structured report and recommended fixes.

Frequently Asked Questions about validate-spec

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

FAQPage Schema
How do I validate an OpenAPI spec and fix structural errors?

You can validate OpenAPI specs by generating a structured report that detects structural, semantic, and schema errors, then applying deterministic fixes to the corrected document.

Why does my OpenAPI specification fail linting and break code generation?

OpenAPI specifications fail linting due to subtle structural or semantic errors. Validation identifies these issues with precise JSON path references and plain-language explanations of how they affect tooling.

Does OpenAPI validation work for both version 2.0 and 3.x documents?

Yes, OpenAPI validation supports documents ranging from version 2.0 through 3.2, detecting structural, semantic, and schema errors across these specifications.

Can I automatically fix OpenAPI validation errors and re-validate the document?

Yes, after identifying validation errors, you can apply proposed deterministic fixes or auto-fix options and immediately demonstrate re-validation on the corrected specification.

How do I locate specific schema errors in a large OpenAPI document?

Schema errors are located using precise JSON path references that point to the exact location in the OpenAPI document, accompanied by a plain-language rationale for each issue.