openapi
OpenAPI/Swagger specification, code generation, documentation, and validation.
Best use case
openapi is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
OpenAPI/Swagger specification, code generation, documentation, and validation.
Teams using openapi should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openapi/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openapi Compares
| Feature / Agent | openapi | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
OpenAPI/Swagger specification, code generation, documentation, and validation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# OpenAPI Skill
Expert assistance for creating OpenAPI specifications and API documentation.
## Capabilities
- Write OpenAPI 3.x specifications
- Generate client/server code
- Create interactive documentation
- Validate API contracts
- Design request/response schemas
## Usage
Invoke this skill when you need to:
- Document REST APIs
- Generate API clients
- Validate API contracts
- Create interactive docs
## Specification Pattern
```yaml
openapi: 3.0.3
info:
title: Users API
version: 1.0.0
paths:
/users:
get:
summary: List users
parameters:
- name: page
in: query
schema:
type: integer
default: 1
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/UserList'
components:
schemas:
User:
type: object
required: [id, name, email]
properties:
id:
type: string
name:
type: string
email:
type: string
format: email
```
## Best Practices
- Use $ref for reusable schemas
- Document all responses
- Include examples
- Version your specs
## Target Processes
- api-documentation
- api-design
- client-generationRelated Skills
openapi-swagger
Expert skill for OpenAPI/Swagger specification analysis, validation, and documentation generation. Parse and validate specs, detect breaking changes, generate code samples, and lint for best practices.
openapi-validator
Validate OpenAPI specifications for correctness, security, and best practices
openapi-spec-generator
Automated OpenAPI specification generation from code annotations, comments, and interface definitions
openapi-codegen-orchestrator
Orchestrate multi-language SDK generation from OpenAPI specifications. Configure OpenAPI Generator per language, apply custom templates and post-processing, handle edge cases and custom extensions, and validate generated code compilation.
openapi-generator
Generate OpenAPI specifications from code or legacy APIs with schema inference and documentation
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.