openapi-spec-generation

Generate and validate OpenAPI 3.1 specifications from code or design sources.

4|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Data-Wise/craft --skill openapi-spec-generation-data-wise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi-spec-generation
Source: https://github.com/Data-Wise/craft/tree/main/skills/docs/openapi-spec-generation
Command: npx skills add https://github.com/Data-Wise/craft --skill openapi-spec-generation-data-wise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenAPI spec generation addresses the challenge of keeping API documentation in sync with code and design specs by producing a reliable OpenAPI 3.1 specification.

Core Features & Use Cases

  • Generates OpenAPI 3.1 specs from code (code-first) or from design-first designs.
  • Validates specs against schemas and integrates with SDK generation pipelines.
  • Supports documentation portals and contract validation across API lifecycles.

Quick Start

Run an OpenAPI generation workflow to produce a ready-to-document 3.1 specification from your codebase.

Frequently Asked Questions about openapi-spec-generation

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

FAQPage Schema
How do I generate OpenAPI 3.1 specifications from existing code?

You can generate OpenAPI 3.1 specifications from your codebase using a code-first workflow. This process automates spec creation directly from your source code, ensuring your API documentation stays synchronized with your implementation.

What is the best way to keep API documentation in sync with design-first sources?

Keeping API documentation in sync is achieved by generating and validating OpenAPI 3.1 specifications from design-first sources. This enforces structure guidelines and provides templates to maintain accurate API definitions throughout the lifecycle.

Can I validate OpenAPI specs against schemas for client SDK generation?

Yes, you can validate OpenAPI specs against schemas to ensure contract compliance. This validation integrates directly with SDK generation pipelines, enabling automated client SDK generation from your validated OpenAPI 3.1 specifications.

Does this approach support both code-first and design-first API workflows?

Yes, this approach supports both code-first and design-first workflows across API projects. It automates the creation and maintenance of OpenAPI 3.1 specifications, whether you are generating docs from existing code or validating designs before implementation.

How do I integrate OpenAPI validation into API documentation portals?

You integrate OpenAPI validation by enforcing 3.1 structure guidelines and using provided templates. This supports documentation portals and contract validation across the entire API lifecycle, ensuring reliable and consistent API documentation.

Why should I use OpenAPI 3.1 specifications for API contract validation?

Using OpenAPI 3.1 specifications for API contract validation solves the challenge of keeping documentation aligned with code. It provides a reliable standard for structure guidelines, enabling consistent validation, documentation, and client SDK generation.