generate-oas
Generate a complete OpenAPI 3.0 (OAS) specification from an API codebase, a Postman or Insomnia collection, or both together. Use this skill whenever the user wants to generate, create, or derive an OpenAPI spec, reverse-engineer an API definition, document an existing API, or convert a Postman/Insomnia collection to OpenAPI — when there is no existing OAS file yet. Triggers on phrases like "generate OAS", "create an OpenAPI spec", "generate openapi.json", "document my API", "reverse-engineer spec", "convert postman to openapi", "convert insomnia to openapi", "postman collection to OAS", "insomnia collection to OAS", or any request to produce an OAS file from source material rather than from an existing spec.
Install
With your agent
Install OMGSkills skill "42crunch-ai/claude-plugins:plugins/api-security-testing/skills/generate-oas" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/42Crunch-AI/claude-plugins /tmp/claude-plugins && ln -s /tmp/claude-plugins/plugins/api-security-testing/skills/generate-oas ~/.claude/skills/generate-oasFrom README
Generate an OpenAPI Specification Produces a complete, valid OpenAPI 3.0.x specification file (openapi.json) from one or two source materials: an API codebase (any language/framework), and/or an API client collection — either a Postman collection (v2.0 or v2.1, with an optional environment file) or an Insomnia collection (v4 JSON export, or v5 JSON/YAML export, with an optional separate environment export) No existing OAS file is required. When both a codebase and a collection are available, the codebase is treated as the primary source of truth for structure — routes, validation, security — and the collection is used to enrich the result with concrete, real-world examples and to surface any endpoint the codebase analysis missed. --- Entry Point Ask about sources one at a time, codebase first, in this order.