Agent skill · software engineering · sickn33
postman-openapi-converter
Convert OpenAPI 3.x or Swagger 2.0 specs (YAML or JSON) into complete, import-ready Postman Collection v2.1 JSON files.
Why this skill is useful
Adds specific mapping procedures and example generation logic for converting OpenAPI specs to Postman collections that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
OpenAPI → Postman Collection Converter When to Use Use this skill when you need convert OpenAPI 3.x or Swagger 2.0 specs (YAML or JSON) into complete, import-ready Postman Collection v2.1 JSON files. Use this skill whenever the user provides or references an OpenAPI spec, Swagger file, openapi.yaml, swagger.json, or uses phrases like "convert my OpenAPI spec",... Converts OpenAPI 3.x or Swagger 2.0 specs into a valid Postman Collection v2.1. --- Step 1 — Detect & Validate Input Identify the spec version from the input: openapi: 3.x.x → OpenAPI 3 swagger: "2.0" → Swagger 2 If the input is truncated or partial, convert what's available and note missing sections. --- Step 2 — Extraction Mapping OpenAPI 3 → Postman OpenAPI field Postman mapping --- --- info.title Collection name info.description Collection description servers[0].url {{baseurl}} variable paths.<path>.<method> One request item per operation operationId or summary Request name parameters (path/query/header) URL path variables, query params, headers requestBody.content.application/json.schema Body (raw JSON), generate example from schema responses Saved example responses components.securitySchemes Collection-level auth tags Folder grouping Swagger 2 → Postman Swagger field Postman mapping --- --- host + basePath {{baseurl}} paths.<path>.<method> Request item parameters Query/path/header/body params consumes / produces Content-Type / Accept headers securityDefinitions Collection auth tags Folders --- Step 3 — Generate Example Bodies For each request with a requestBody or body parameter, generate a realistic example JSON body from the schema: Use property names as keys Infer sensible example values from type + format (e.g., "email" format → "user@example.com", "date-time" → "2024-01-15T10:30:00Z") For $ref schemas, resolve them inline --- Step 4 — Auth Handling Map security schemes to Postman auth: OpenAPI scheme Postman auth type --- --- http: bearer bearer with {{token}} http: basic basic with {{username}} …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/postman-openapi-converter