| name | api-testing |
| description | Use this skill when you need to design API test plans or cases for REST, GraphQL, or gRPC interfaces; triggers include API testing and API test cases. |
API Testing (English)
中文版： 见对应中文技能。
When to Use
- Need an API test plan, API cases, or API risk analysis.
- The request involves REST, GraphQL, SOAP, gRPC, WebSocket, or mixed API behavior.
Output Format Options
Markdown by default. If you need Excel, CSV, JSON, Word, or other supported formats, append the format request at the end and check output-formats.md.
How to Use
- Open
prompts/api-testing.md and 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-testing.md: main prompt for this skill.output-formats.md: optional output format instructions.references/: supporting notes loaded only when needed.scripts/: helper scripts or converters for this skill.
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.
