postman2pytest
Convert a Postman Collection v2.1 JSON file into a runnable pytest test suite using the postman2pytest CLI. Use when the user has a Postman collection (a .postman_collection.json or v2.1 JSON export) and wants to run it as pytest in CI, when migrating from Postman/Newman to a Python-native test stack, when bridging Postman-documented APIs into a pytest-based regression suite, when the user asks to generate pytest tests from Postman, or when the user mentions wanting to keep Postman as the source of truth but run the suite with pytest.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly specifies the concrete action (converting Postman v2.1 JSON to pytest), names the specific tool (postman2pytest CLI), and provides comprehensive 'Use when' triggers covering multiple realistic user scenarios. The trigger terms are natural and varied, covering migration, CI, and documentation use cases, making it highly discoverable and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists concrete actions: 'Convert a Postman Collection v2.1 JSON file into a runnable pytest test suite using the postman2pytest CLI.' This names the specific input format, output artifact, and the tool used. | 3 / 3 |
Completeness | Clearly answers both 'what' (convert Postman Collection v2.1 JSON into a runnable pytest test suite) and 'when' with an explicit 'Use when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Postman collection', '.postman_collection.json', 'v2.1 JSON export', 'pytest', 'CI', 'Newman', 'Python-native test stack', 'regression suite', 'generate pytest tests from Postman', 'source of truth'. These cover many natural phrasings a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: the intersection of Postman collections and pytest generation is very specific and unlikely to conflict with general testing skills, general Postman skills, or general pytest skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with clear CLI commands and a well-structured Quick Start workflow. Its main weaknesses are the lack of validation/error-recovery steps in the workflow (e.g., what to do when conversion fails or tests don't pass) and some unnecessary verbosity in the 'When to invoke' and 'Example walkthrough' sections that describe rather than instruct. The limitations section is honest and useful but could be more concise.
Suggestions
Add validation checkpoints to the workflow: e.g., verify the collection is v2.1 before running the converter, check the generated file exists, and provide guidance on common conversion errors.
Trim or remove the 'When to invoke' section — this is trigger/metadata information better suited to the YAML frontmatter or a brief one-liner, not a full enumerated list.
Replace the descriptive 'Example walkthrough' with actual command output (e.g., show the terminal output of postman2pytest and pytest -v) to make it more actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like 'When to invoke' (which is metadata-level guidance Claude doesn't need in the body) and the 'Example walkthrough' section is descriptive rather than showing actual output. The 'What it does not do' section is useful but slightly verbose. | 2 / 3 |
Actionability | The Quick Start provides fully executable, copy-paste-ready commands with clear sequencing: install, run converter, set env var, run tests, commit. CLI flags like --filter-folder and --collection are concrete and specific. | 3 / 3 |
Workflow Clarity | The 5-step Quick Start is clearly sequenced, but there are no validation checkpoints or error recovery steps. What happens if the collection is v1? What if the conversion fails? What if tests fail? No feedback loops are provided for these scenarios. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in a single file with no bundle files for advanced topics. The 'Limitations and known gaps' section punts to external issues without providing actionable detail. References to external URLs are present but no internal file references exist. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- golikovichev/postman2pytest
- Commit
fdd9694
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.