openapi

Design, evolve, and govern OpenAPI contracts for production HTTP APIs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kittne/codex-skills-by-codex --skill openapi-kittne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openapi
Source: https://github.com/kittne/codex-skills-by-codex/tree/main/openapi
Command: npx skills add https://github.com/kittne/codex-skills-by-codex --skill openapi-kittne

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design, evolve, and govern OpenAPI contracts for production HTTP APIs with compatibility, security, and tooling reliability.

Core Features & Use Cases

  • Schema modeling and operation design for consistent API contracts
  • Reusable components, version strategy, linting, and diff-based governance
  • Security and compatibility governance across client and server implementations

Quick Start

Identify your API audience and lifecycle needs, then draft and validate an OpenAPI contract following the workflow guidelines.

Frequently Asked Questions about openapi

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

FAQPage Schema
How do I govern OpenAPI contracts to ensure backward compatibility during API versioning?

You can govern OpenAPI contracts by applying diff-based checks and linting to ensure safe API versioning. This approach validates schema evolution, enforces reusable components, and verifies that changes maintain backward compatibility across client and server implementations.

How do I design and evolve production HTTP API contracts with security and compatibility governance?

You design and evolve production HTTP APIs by enforcing reusable components, stable operationId values, and central security definitions. This workflow applies schema modeling, version strategy, and automated validation to maintain compatibility and security across client and server implementations.

What is the best way to lint and validate OpenAPI schema models for automated delivery workflows?

The best way to lint and validate OpenAPI schema models is through diff-based governance and automated validation checks. This enforces contract stability, security definitions, and reusable components to ensure safe schema evolution within automated delivery workflows.

Does this approach to API contract governance work for both internal and public services?

Yes, this approach works for both internal and public services. It governs OpenAPI contracts by enforcing security definitions, compatibility checks, and schema modeling, ensuring reliable API operations regardless of the target audience or service exposure level.

Why do my OpenAPI contract changes break existing client implementations?

OpenAPI contract changes break clients when compatibility is not governed. You can prevent this by using linting and diff checks to validate changes, enforcing stable operationId values, and maintaining reusable components to ensure safe contract evolution.