Postman API Testing (EN)
Chinese version: See the corresponding Chinese skill.
When to Use
- Need outputs that should land in a Postman API testing workflow.
- The project already uses Postman or wants Postman-ready planning.
Output Format Options
Markdown by default unless the request explicitly asks for another format.
How to Use
- Open
prompts/api-test-postman.mdand use it as the main prompt. - Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.
- If the input is incomplete, return a usable first version and mark missing information and assumptions.
Reference Files
prompts/api-test-postman.md: main prompt for this skill.references/framework-spec.md: tool-specific structure and coverage notes.references/setup-and-ci.md: setup, execution, and CI notes.examples/sample-context.md: sample request context.scripts/run-tests.sh: lightweight local execution entry point.
Common Pitfalls
- Do not use it with vague scope and no context.
- Do not treat every area as equally important.
- Do not skip assumptions and missing information.
Best Practices
- Start from the prompt file, then add only the context that matters.
- Keep the output risk-driven and executable.
- If the request is incomplete, return a usable first version and mark gaps.