openapi-spec-reviewer

Audit OpenAPI 3.0/3.1 specifications and generate severity-ranked documentation reports.

1|1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/in-co-sandbox/in-co-sandbox-docs --skill openapi-spec-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi-spec-reviewer
Source: https://github.com/in-co-sandbox/in-co-sandbox-docs/tree/main/ai/skills/openapi-spec-reviewer
Command: npx skills add https://github.com/in-co-sandbox/in-co-sandbox-docs --skill openapi-spec-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure your OpenAPI specifications are clear, accurate, and function as high-quality documentation, making APIs easier to understand and use.

Core Features & Use Cases

  • OpenAPI Specification Auditing: Reviews OpenAPI (OAS 3.0/3.1) specifications for documentation quality.
  • Endpoint Documentation Improvement: Enhances operation summaries, descriptions, and examples.
  • Doc Quality Validation: Validates documentation quality for specific endpoints referenced in MDX files.
  • Severity-Ranked Reports: Produces concrete, actionable OpenAPI change recommendations.
  • Use Case: You have an openapi.json file and want to ensure all operation summaries and descriptions are clear, and that response schemas include examples. This Skill will analyze the spec and provide a report with specific suggestions.

Quick Start

Use the openapi-spec-reviewer skill to audit the OpenAPI specification file located at api-reference/gst/compliance/openapi.json for the POST /gst/compliance/e-way-bill/tax-payer/authenticate endpoint.

Frequently Asked Questions about openapi-spec-reviewer

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

FAQPage Schema
How do I audit an OpenAPI specification for documentation quality?

To audit an OpenAPI specification, you can review operation summaries, descriptions, and examples against endpoint MDX wrappers to generate severity-ranked reports with concrete OAS 3.0/3.1 changes.

Can I validate OpenAPI endpoint documentation against MDX wrappers?

Yes, you can validate OpenAPI endpoint documentation quality by checking operation definitions against specific endpoints referenced in MDX files to ensure consistency and accuracy.

Does this tool work with OAS 3.1 specifications?

Yes, the specification review process supports both OAS 3.0 and OAS 3.1 formats, analyzing your OpenAPI files to enhance documentation quality and produce actionable improvement reports.

How do I improve missing examples in my OpenAPI spec?

You can improve missing examples by analyzing your OpenAPI spec to identify gaps in response schemas and operation descriptions, then applying concrete suggestions from a severity-ranked report.

What is the best way to generate actionable OpenAPI documentation reports?

The best way to generate actionable OpenAPI documentation reports is to run Python analysis scripts that audit summaries and examples, producing severity-ranked recommendations for concrete spec changes.