About api-test-postman
A skill for producing Postman-oriented API testing plans and outputs. It guides users to add project context, account for risks, and mark gaps or assumptions when information is incomplete.
Key features
- 01Postman-ready API test planning
- 02Project-context guidance
- 03Risk-driven output
- 04Assumption and gap tracking
- 05Markdown output by default
Use cases
- 01Preparing API tests for a Postman workflow
- 02Planning tests for an existing Postman project
- 03Drafting an initial plan with incomplete inputs
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/api-test-postmanin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
README.mdagents/openai.yamlevals/eval.yamlevals/cases/basic-success.yamledge-incomplete-input.yamledge-scope-boundary.yamlreview-collection-auth-cleanup.yamlreview-unknown-expectation.yamlexamples/sample-context.mdoutput-templates/template-markdown.mdprompts/api-test-postman.mdreferences/framework-spec.mdsetup-and-ci.mdscripts/run-tests.shDetails
From the project READMEPostman 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.
Comments
Markdown supported