git:20260807.3bfc411 to git:20260903.6713296

4 added, 4 removed. Audit A to A.

---

name: api-test-postman

- description: Use this skill when you need design Postman collections, environments, scripts, and Newman-ready API regression plans.; triggers include API Test Postman, API testing, and api-test-postman.

+ description: Use this skill when you need to design Postman collections, environments, scripts, and Newman-ready API regression plans; triggers include Postman API testing, API testing, and api-test-postman.

---

- # API Test Postman (EN)

+ # Postman API Testing (EN)

- **中文版：** 见对应中文技能。

+ **Chinese version：** See the corresponding Chinese skill.

## When to Use

- - Need outputs that should land in a API Test Postman-oriented workflow.

+ - 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

1. Open `prompts/api-test-postman.md` and use it as the main prompt.

2. Add the real project context: scope, environment, constraints, risks, dependencies, and expected deliverable.

3. 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.