Update to Postman

{
  "canonical_app_id": "asdk_app_6a6b12e06c5c8191ac5d5252fa5f92c8",
  "connector_id": "asdk_app_6a6b12e06c5c8191ac5d5252fa5f92c8",
  "created_at": "2026-07-30T09:01:20.695549Z",
  "discoverability": "LISTED",
  "id": "plugin_asdk_app_6a6b12e06c5c8191ac5d5252fa5f92c8",
  "is_template": false,
  "is_template_instance": false,
  "name": "app-6a6b12e06c5c8191ac5d5252fa5f92c8",
  "release": {
    "app_ids": [
      "asdk_app_6a6b12e06c5c8191ac5d5252fa5f92c8"
    ],
    "app_manifest": {
      "apps": {
        "postman": {
          "id": "asdk_app_6a6b12e06c5c8191ac5d5252fa5f92c8",
          "required": true
        }
      }
    },
    "app_templates": [],
    "description": "Equip Codex with specialized Postman skills for the complete API lifecycle. Discover, design, test, document, mock, monitor, and improve APIs through agent-friendly, filesystem-first workflows",
    "display_name": "Postman",
    "id": "pluginrel_8abe03ee26f48191b8dd111bf3e3c79f",
    "interface": {
      "brand_color": null,
      "capabilities": [],
      "category": "Developer Tools",
      "composer_icon_dark_url": null,
      "composer_icon_url": "https://files.openai.com/content?id=file_0000000087a48211815f23ac98904492",
      "default_prompt": "create a collection for the API in this repo, add tests, and run them",
      "default_prompts": [
        "create a collection for the API in this repo, add tests, and run them",
        "turn this OpenAPI spec into a working mock server",
        "is this API Agent ready?"
      ],
      "developer_name": "Postman",
      "logo_url": "https://files.openai.com/content?id=file_000000007e5c81f4a53093435baedf63",
      "logo_url_dark": null,
      "long_description": "Equip Codex with specialized Postman skills for the complete API lifecycle. Discover, design, test, document, mock, monitor, and improve APIs through agent-friendly, filesystem-first workflows",
      "plugin_category_id": "developer tools",
      "privacy_policy_url": "https://privacy.postman.com/policies/",
      "screenshot_urls": [],
      "short_description": "API Engineering for Agents",
      "terms_of_service_url": "https://www.postman.com/legal/terms/",
      "website_url": "https://www.postman.com/"
    },
    "keywords": [],
    "onboarding_skill_name": null,
    "requires_local_executor": false,
    "skills": [
      {
        "description": "Use when assessing or improving how well AI agents can discover, call, and recover from errors with an API. Scores an existing Postman collection or OpenAPI spec and turns measured gaps into contract improvements; supports a separate CI readiness threshold. Use for requests such as \"is this API ready for agents\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "ai-readiness",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Use when assessing or improving how well AI agents can discover, call, and recover from errors with an API. Scores an existing Postman collection or OpenAPI spec and turns measured gaps into contract improvements; supports a separate CI readiness threshold. Use for requests such as \"is this API ready for agents\"."
        },
        "name": "ai-readiness",
        "plugin_release_skill_id": "pluginrsk_6aea1636905c8191b636fde202c1df69"
      },
      {
        "description": "Use when finding an API or owner, integrating a public provider, locating Postman resources, or investigating consumers and change impact across services. Turns discovered contracts and mocks into reusable dependencies and identifies evidence outside the current checkout. Use for requests such as \"who consumes this endpoint\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-discovery",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "search",
          "short_description": "Use when finding an API or owner, integrating a public provider, locating Postman resources, or investigating consumers and change impact across services. Turns discovered contracts and mocks into reusable dependencies and identifies evidence outside the current checkout. Use for requests such as \"who consumes this endpoint\"."
        },
        "name": "api-discovery",
        "plugin_release_skill_id": "pluginrsk_6aea163c26488191ba4c4b917ca93e4f"
      },
      {
        "description": "Use when defining or improving an API contract, generating documentation from a collection or OpenAPI spec, publishing API docs, or sharing a documentation link. Makes auth, inputs, responses, and examples reusable by callers, tests, and mocks. Use for requests such as \"publish API docs\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-documentation",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Use when defining or improving an API contract, generating documentation from a collection or OpenAPI spec, publishing API docs, or sharing a documentation link. Makes auth, inputs, responses, and examples reusable by callers, tests, and mocks. Use for requests such as \"publish API docs\"."
        },
        "name": "api-documentation",
        "plugin_release_skill_id": "pluginrsk_6aea163709f48191ba27a8344e1536b1"
      },
      {
        "description": "Use when designing, implementing, mocking, testing, monitoring, documenting, or deploying an API. Guides decisions using reusable local API contracts, tests, and mocks, plus organization-wide dependency context, and routes to the relevant Postman skills. Use for requests such as \"implement this endpoint\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-engineer",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Use when designing, implementing, mocking, testing, monitoring, documenting, or deploying an API. Guides decisions using reusable local API contracts, tests, and mocks, plus organization-wide dependency context, and routes to the relevant Postman skills. Use for requests such as \"implement this endpoint\"."
        },
        "name": "api-engineer",
        "plugin_release_skill_id": "pluginrsk_6aea1639d7c481918b12392df013aea9"
      },
      {
        "description": "Finds, builds, runs and publishes a stand-in for one API — the owning team's published mock when there is one, otherwise one built from its spec or collection that behaves like the real API, stateful when callers write then read. Use when something needs an API that isn't built or reachable yet (a frontend, client or demo), when other teams should build against your API before it ships, or when asked to mock an API or fake a backend. To run and test your own code against the services it calls, use api-simulation. Covers `postman mock` and `postman dependency add mock`.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-mocking",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Finds, builds, runs and publishes a stand-in for one API — the owning team's published mock when there is one, otherwise one built from its spec or collection that behaves like the real API, stateful when callers write then read. Use when something needs an API that isn't built or reachable yet (a frontend, client or demo), when other teams should build against your API before it ships, or when asked to mock an API or fake a backend. To run and test your own code against the services it calls, use api-simulation. Covers `postman mock` and `postman dependency add mock`."
        },
        "name": "api-mocking",
        "plugin_release_skill_id": "pluginrsk_6aea163606ec8191b808867a0cc6ce7d"
      },
      {
        "description": "Use when setting up recurring API checks, running or diagnosing a Postman Monitor, changing its schedule, or reaching private APIs through a self-hosted runner. Reuses collection assertions to detect live regressions and traces failures to individual run evidence. Use for requests such as \"check this API every minute\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-monitoring",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Use when setting up recurring API checks, running or diagnosing a Postman Monitor, changing its schedule, or reaching private APIs through a self-hosted runner. Reuses collection assertions to detect live regressions and traces failures to individual run evidence. Use for requests such as \"check this API every minute\"."
        },
        "name": "api-monitoring",
        "plugin_release_skill_id": "pluginrsk_6aea16369c9c8191b64817648ab7e00c"
      },
      {
        "description": "Runs services, frontends, tests or demos against stand-ins for their HTTP dependencies, served as one environment locally or at a deployed URL. Use when you add or change code that calls other services and need to run it, test it, prove a fix or reproduce an upstream failure (timeouts, 5xx, 409, 429) end to end, locally or in CI, without the real services because they're unreachable, need credentials, cost money, have side effects or don't exist yet. Also answers what happens to a request, or to the data it writes, when a service it calls goes down, is slow or returns errors (\"what happens to a booking if the email service is down?\"), by exercising relevant failures and observing caller outcomes. Applies even when nobody says mock or simulation, and a `postman/simulations/` directory in the repository is itself a reason to load this before changing code it covers. To give a frontend or another team a stand-in for an API, use api-mocking. Covers `postman simulation`.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-simulation",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Runs services, frontends, tests or demos against stand-ins for their HTTP dependencies, served as one environment locally or at a deployed URL. Use when you add or change code that calls other services and need to run it, test it, prove a fix or reproduce an upstream failure (timeouts, 5xx, 409, 429) end to end, locally or in CI, without the real services because they're unreachable, need credentials, cost money, have side effects or don't exist yet. Also answers what happens to a request, or to the data it writes, when a service it calls goes down, is slow or returns errors (\"what happens to a booking if the email service is down?\"), by exercising relevant failures and observing caller outcomes. Applies even when nobody says mock or simulation, and a `postman/simulations/` directory in the repository is itself a reason to load this before changing code it covers. To give a frontend or another team a stand-in for an API, use api-mocking. Covers `postman simulation`."
        },
        "name": "api-simulation",
        "plugin_release_skill_id": "pluginrsk_6aea1639640c8191b36aeefff48aaec2"
      },
      {
        "description": "Use when testing an endpoint, running collection assertions, or checking real application traffic against an API contract. Reuses saved requests and reports what live, mocked, or captured-traffic results actually establish. Use for requests such as \"test this endpoint\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "api-testing",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Use when testing an endpoint, running collection assertions, or checking real application traffic against an API contract. Reuses saved requests and reports what live, mocked, or captured-traffic results actually establish. Use for requests such as \"test this endpoint\"."
        },
        "name": "api-testing",
        "plugin_release_skill_id": "pluginrsk_6aea163b86b08191a58ba769fd80f8ec"
      },
      {
        "description": "Sets up, runs, debugs, and interprets results from `postman application test` — the Postman layer that runs your Playwright tests, captures their network traffic, matches it against a collection contract, runs pm.test assertions, and publishes results to Application Inventory. Covers the Postman side of the integration only — not Playwright test authoring or Playwright failures unrelated to capture. Use when the user asks to \"set up application testing,\" \"test my application with Postman,\" \"connect my Playwright tests to Postman,\" \"capture network traffic from Playwright,\" \"Playwright tests are running but nothing shows up in Postman,\" \"why isn't application testing capturing anything,\" \"exclude certain requests from capture,\" \"generate a collection from my app's traffic,\" \"set up application testing in CI,\" \"what API coverage do my e2e tests have,\" \"which APIs are my Playwright tests not hitting.\"",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "application-testing",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Sets up, runs, debugs, and interprets results from `postman application test` — the Postman layer that runs your Playwright tests, captures their network traffic, matches it against a collection contract, runs pm.test assertions, and publishes results to Application Inventory. Covers the Postman side of the integration only — not Playwright test authoring or Playwright failures unrelated to capture. Use when the user asks to \"set up application testing,\" \"test my application with Postman,\" \"connect my Playwright tests to Postman,\" \"capture network traffic from Playwright,\" \"Playwright tests are running but nothing shows up in Postman,\" \"why isn't application testing capturing anything,\" \"exclude certain requests from capture,\" \"generate a collection from my app's traffic,\" \"set up application testing in CI,\" \"what API coverage do my e2e tests have,\" \"which APIs are my Playwright tests not hitting.\""
        },
        "name": "application-testing",
        "plugin_release_skill_id": "pluginrsk_6aea163c1cd08191b3f050c55baa4b79"
      },
      {
        "description": "Use when adding API tests, structural or governance lint, or AI-readiness gates to CI, or publishing reviewed API artifacts to a Postman workspace after merge. Makes contract checks repeatable and separates validation from shared workspace changes. Use for requests such as \"run this collection on every PR\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "ci-integration",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Use when adding API tests, structural or governance lint, or AI-readiness gates to CI, or publishing reviewed API artifacts to a Postman workspace after merge. Makes contract checks repeatable and separates validation from shared workspace changes. Use for requests such as \"run this collection on every PR\"."
        },
        "name": "ci-integration",
        "plugin_release_skill_id": "pluginrsk_6aea1639db04819198d60fc25f790a11"
      },
      {
        "description": "Use when the Postman CLI is missing or can't be installed, or when `postman` is \"command not found\". Installs the CLI globally so `postman` is on `PATH`, with a fallback to the hosted MCP server when installing is blocked. Use for requests such as \"install the Postman CLI\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "cli-install",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "bolt",
          "short_description": "Use when the Postman CLI is missing or can't be installed, or when `postman` is \"command not found\". Installs the CLI globally so `postman` is on `PATH`, with a fallback to the hosted MCP server when installing is blocked. Use for requests such as \"install the Postman CLI\"."
        },
        "name": "cli-install",
        "plugin_release_skill_id": "pluginrsk_6aea1637d6c081919781bf5a7ecad061"
      },
      {
        "description": "Use when writing or debugging local Postman v3 collection, environment or globals files, including collection lint failures. Preserves the per-entity files, inherited context, and schema shapes that make API changes reusable and reviewable in Git. Use for requests such as \"fix this request YAML\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "collection-schema-v3",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Use when writing or debugging local Postman v3 collection, environment or globals files, including collection lint failures. Preserves the per-entity files, inherited context, and schema shapes that make API changes reusable and reviewable in Git. Use for requests such as \"fix this request YAML\"."
        },
        "name": "collection-schema-v3",
        "plugin_release_skill_id": "pluginrsk_6aea1637c564819186170fbcbf8c4010"
      },
      {
        "description": "Use when creating or repairing dataset manifests, or when a collection needs queried or joined test inputs, a reusable named view, spreadsheet worksheet data, live database rows, or script access through pm.datasets(). Chooses between a simple iteration file and a dataset while preserving query semantics, portability, and credential boundaries. Use for requests such as \"run this collection over database rows\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "datasets",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Use when creating or repairing dataset manifests, or when a collection needs queried or joined test inputs, a reusable named view, spreadsheet worksheet data, live database rows, or script access through pm.datasets(). Chooses between a simple iteration file and a dataset while preserving query semantics, portability, and credential boundaries. Use for requests such as \"run this collection over database rows\"."
        },
        "name": "datasets",
        "plugin_release_skill_id": "pluginrsk_6aea163a58748191b3c3ae2818a8fd66"
      },
      {
        "description": "Use when running, deploying, or debugging an existing Postman Flow. Distinguishes local graph execution from a deployed webhook, reuses named input scenarios, and follows a run to the failing block rather than treating an HTTP response as whole-flow success. Use for requests such as \"why did this flow fail\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "flows",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "bolt",
          "short_description": "Use when running, deploying, or debugging an existing Postman Flow. Distinguishes local graph execution from a deployed webhook, reuses named input scenarios, and follows a run to the failing block rather than treating an HTTP response as whole-flow success. Use for requests such as \"why did this flow fail\"."
        },
        "name": "flows",
        "plugin_release_skill_id": "pluginrsk_6aea163d32708191a0ad8c652d1b8503"
      },
      {
        "description": "Use when load-testing or benchmarking an API with concurrent virtual users and latency or error thresholds, or when importing or migrating a JMeter `.jmx` plan or a Gatling simulation (Java/Kotlin/Scala/JS/TS) into a Postman collection plus a `postman performance run` configuration. Reuses a collection to probe a chosen failure mode and distinguishes target limits from load-generator limits. Use for requests such as \"load test this API\", \"import my JMeter plan\", or \"convert my Gatling project to Postman\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "performance-testing",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "chart",
          "short_description": "Use when load-testing or benchmarking an API with concurrent virtual users and latency or error thresholds, or when importing or migrating a JMeter `.jmx` plan or a Gatling simulation (Java/Kotlin/Scala/JS/TS) into a Postman collection plus a `postman performance run` configuration. Reuses a collection to probe a chosen failure mode and distinguishes target limits from load-generator limits. Use for requests such as \"load test this API\", \"import my JMeter plan\", or \"convert my Gatling project to Postman\"."
        },
        "name": "performance-testing",
        "plugin_release_skill_id": "pluginrsk_6aea163d6588819184e4dd33b83ff1b6"
      },
      {
        "description": "Use when working through Postman MCP tools to inspect or change workspace resources, choose a targeted operation, or handle MCP limitations. Supports hosted workflows when the CLI is unavailable and distinguishes tool completion from a usable result. Use for requests such as \"use Postman MCP to inspect this collection\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "postman-mcp-server",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "code",
          "short_description": "Use when working through Postman MCP tools to inspect or change workspace resources, choose a targeted operation, or handle MCP limitations. Supports hosted workflows when the CLI is unavailable and distinguishes tool completion from a usable result. Use for requests such as \"use Postman MCP to inspect this collection\"."
        },
        "name": "postman-mcp-server",
        "plugin_release_skill_id": "pluginrsk_6aea163d55a8819180dea238c5f231f4"
      },
      {
        "description": "Use when parameterizing requests across environments, choosing variable scopes, chaining values in scripts, or referencing credentials without committing or exposing them. Keeps one reusable collection while separating target configuration from secret values. Use for requests such as \"where should I put this API key\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "variables",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Use when parameterizing requests across environments, choosing variable scopes, chaining values in scripts, or referencing credentials without committing or exposing them. Keeps one reusable collection while separating target configuration from secret values. Use for requests such as \"where should I put this API key\"."
        },
        "name": "variables",
        "plugin_release_skill_id": "pluginrsk_6aea163c64dc8191804530b710fc31f0"
      },
      {
        "description": "Capture, forward to localhost, replay, and validate webhook deliveries using a reusable public URL. Keep sender configuration across debugging sessions and record arrivals even while local forwarding is stopped, helping distinguish delivery failures from local connectivity issues. Use for implementing or debugging incoming handlers and testing webhooks an API sends, whether or not Postman is mentioned. Example requests include \"get payment events to localhost,\" \"inspect a webhook delivery,\" and \"replay an event after a fix\"; these illustrate intent, not an exhaustive list or exact phrases to match.",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "webhook-testing",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "radar",
          "short_description": "Capture, forward to localhost, replay, and validate webhook deliveries using a reusable public URL. Keep sender configuration across debugging sessions and record arrivals even while local forwarding is stopped, helping distinguish delivery failures from local connectivity issues. Use for implementing or debugging incoming handlers and testing webhooks an API sends, whether or not Postman is mentioned. Example requests include \"get payment events to localhost,\" \"inspect a webhook delivery,\" and \"replay an event after a fix\"; these illustrate intent, not an exhaustive list or exact phrases to match."
        },
        "name": "webhook-testing",
        "plugin_release_skill_id": "pluginrsk_6aea163663ac8191a0005ed071c39156"
      },
      {
        "description": "Use when initializing Postman in a repository, binding it to a Postman workspace, interpreting what `postman init` did, or when a CLI command fails because the plan, credits, or usage quota don't allow the operation. Treats the workspace as the place where a service's API work and its evidence live, kept separate from the services it depends on. Use for requests such as \"set up Postman in this repo\" or \"connect this repo to our workspace\".",
        "interface": {
          "brand_color": null,
          "default_prompt": null,
          "display_name": "workspaces",
          "icon_large_url": null,
          "icon_small_url": null,
          "iconography": "hierarchy",
          "short_description": "Use when initializing Postman in a repository, binding it to a Postman workspace, interpreting what `postman init` did, or when a CLI command fails because the plan, credits, or usage quota don't allow the operation. Treats the workspace as the place where a service's API work and its evidence live, kept separate from the services it depends on. Use for requests such as \"set up Postman in this repo\" or \"connect this repo to our workspace\"."
        },
        "name": "workspaces",
        "plugin_release_skill_id": "pluginrsk_6aea1637bc188191b1d9e8f683067a94"
      }
    ],
    "version": "0.6.0"
  },
  "scope": "GLOBAL",
  "status": "ENABLED"
}