English version: see the matching English skill.
When to Use
- When you need to produce a test plan or automation design for a Postman API testing workflow.
- When the project already uses the relevant tools, or you want a tool-specific plan that can be implemented directly.
Output Format Options
Use Markdown by default. Unless the request explicitly asks for another format, do not extend the output format.
How to Use
- Open
prompts/api-test-postman.mdand use it as the main prompt. - Supplement with real project context: scope, environment, constraints, risks, dependencies, and expected deliverables.
- If the input is incomplete, first return a usable first version and mark the missing information and assumptions.
Reference Files
prompts/api-test-postman.md: The main prompt for this skill.references/framework-spec.md: Tool-specific structure and coverage description.references/setup-and-ci.md: Installation, execution, and CI instructions.examples/sample-context.md: Example request context.scripts/run-tests.sh: Lightweight local execution entry point.
Common Pitfalls
- Do not give generic solutions directly when the scope is vague and context is lacking.
- Do not treat all modules and scenarios as equally important.
- Do not skip stating assumptions and missing information.
Best Practices
- Start from the prompt file, and only add context that truly affects the result.
- Keep the output risk-driven and directly usable for execution or review.
- When information is incomplete, first provide a usable version, then clearly mark the gaps.