Skip to content
Skill

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

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
392
Last commit
12 days ago
License
MIT
Listing updated
today

When your agent uses it

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", "import swagger to Postman", "turn this spec into a collection", or "generate Postman requests from my API spec". Also triggers when the user pastes YAML or JSON that begins with `openapi:`, `swagger:`, or contains `paths:` with HTTP method keys. Always prefer this skill over the general collection generator when the input is a structured spec file.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (6 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/postman-openapi-converter to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/LambdaTest/agent-skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/postman-openapi-converter &&
cp -R "$tmp/api-skill/postman/postman-openapi-converter" ~/.claude/skills/postman-openapi-converter &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/postman-openapi-converter inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/postman-openapi-converter to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/LambdaTest/agent-skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/postman-openapi-converter &&
cp -R "$tmp/api-skill/postman/postman-openapi-converter" ~/.agents/skills/postman-openapi-converter &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/postman-openapi-converter inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/postman-openapi-converter to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/LambdaTest/agent-skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/postman-openapi-converter &&
cp -R "$tmp/api-skill/postman/postman-openapi-converter" ~/.cursor/skills/postman-openapi-converter &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/postman-openapi-converter inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/LambdaTest/agent-skills.git --path api-skill/postman/postman-openapi-converter

Or copy the folder to ~/.gemini/skills/postman-openapi-converter yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/postman-openapi-converter:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/LambdaTest/agent-skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/postman-openapi-converter &&
cp -R "$tmp/api-skill/postman/postman-openapi-converter" ~/.copilot/skills/postman-openapi-converter &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/postman-openapi-converter inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/LambdaTest/agent-skills.git

Then copy agent-skills/api-skill/postman/postman-openapi-converter into your agent's skills folder as postman-openapi-converter. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Postman openapi converter FAQ

How do I install Postman openapi converter in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/postman-openapi-converter to use it in all your projects, or to .claude/skills/postman-openapi-converter in one project.

Does Postman openapi converter run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Postman openapi converter?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Postman openapi converter?

The closest alternatives to Postman openapi converter are Rea changelog update, Code review, Gem devops guidelines, PR screenshots and Docs sync audit.

More from LambdaTest/agent-skills

  1. Adds automated accessibility (a11y) testing to test suites on TestMu AI cloud by enabling WCAG scans through driver capabilities

    • Open source
    • 392 GitHub stars
    • Browser automation
  2. Designs AI-powered API features, LLM tool/function definitions, MCP server tool schemas, natural language to API conversion, and agentic API

    • Open source
    • 392 GitHub stars
    • AI models and LLM tooling
  3. Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params)

    • Open source
    • 392 GitHub stars
  4. Designs GDPR-compliant API patterns, PCI-DSS field handling, SOC2 audit log schemas, HIPAA data endpoints, and regulatory compliance checkli

    • Open source
    • 392 GitHub stars
    • Security
  5. Generates complete, production-ready REST API endpoint specifications for any system or domain the user describes

    • Open source
    • 392 GitHub stars
  6. Generate comprehensive, professional API documentation from API designs, endpoint definitions, OpenAPI/Swagger specs, route lists, or raw en

    • Open source
    • 392 GitHub stars
    • Developer tools

Alternatives to Postman openapi converter

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. Run a read-only documentation drift audit for a feature, PR, branch, release, API, configuration change, workflow, CLI, package, or reposito

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  6. Upgrade GitHub Actions to supported runtimes by selecting safe action versions, preserving workflow behavior, and validating post-upgrade ex

    • Open source
    • 41.3K GitHub stars
    • Developer tools