sterlingchin/postman-claude-skill

Overview

This skill provides Postman API lifecycle management directly from Python scripts. It lets you discover workspaces and collections, run tests with Newman, validate and manage API specifications, and publish or inspect documentation and monitors across the full API workflow. First-use validation runs automatically to check your API key and workspace configuration and suggests next steps if setup is incomplete.

How this skill works

All Postman interactions are executed via Python scripts that load your Postman API key from a .env file and call the Postman API server-side, avoiding browser CORS issues. The skill supports collection and spec discovery, schema validation, fork/merge workflows for collections, environment management with secret preservation, Newman-based test execution, mock server creation, and monitor analysis. It includes robust error handling, retry logic, and proxy-aware networking for corporate environments.

When to use it

• You need to list or inventory Postman workspaces, collections, environments, specs, or monitors.
• You want to validate OpenAPI/AsyncAPI schemas or compare API versions before deployment.
• You need to run collection tests and retrieve formatted Newman results.
• You want to generate collections from specs or generate specs from existing collections.
• You need to create forks, open pull requests, or merge collection changes (v10+).
• You need to create mock servers, inspect monitor history, or review documentation quality.

Best practices

• Store POSTMAN_API_KEY and optional settings in a .env file loaded by the scripts.
• Always run the initial setup validation script to confirm connectivity and workspace selection.
• Use the provided Python scripts rather than browser-based API calls to avoid CORS failures.
• Enable POSTMAN_USE_PROXY only if your proxy allows api.getpostman.com; otherwise keep proxy bypass.
• Protect sensitive environment variables by relying on the skill's automatic secret detection and preservation.

Example use cases

• Inventory all collections and environments in a workspace to plan test coverage.
• Validate an OpenAPI spec and generate a Postman collection for automated testing.
• Fork a collection, run changes through Newman, and merge back via the built-in pull request flow.
• Create a mock server for frontend development while backend endpoints are still in progress.
• Set up a monitor to track uptime and analyze run histories for reliability trends.