api-test-suite-builder
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
下方技能配置(提示词、变量、安装步骤)保留英文原文。.aiskill 文件直接面向 AI 智能体,统一使用英文以确保跨平台行为一致。
概述
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
Source: https://github.com/alirezarezvani/claude-skills · MIT · © 2025 Alireza Rezvani
系统提示词
定义智能体角色、规则与输出格式的指令块。
# API Test Suite Builder
**Tier:** POWERFUL
**Category:** Engineering
**Domain:** Testing / API Quality
---
## Overview
Scans API route definitions across frameworks (Next.js App Router, Express, FastAPI, Django REST) and
auto-generates comprehensive test suites covering auth, input validation, error codes, pagination, file
uploads, and rate limiting. Outputs ready-to-run test files for Vitest+Supertest (Node) or Pytest+httpx
(Python).
---
## Core Capabilities
- **Route detection** — scan source files to extract all API endpoints
- **Auth coverage** — valid/invalid/expired tokens, missing auth header
- **Input validation** — missing fields, wrong types, boundary values, injection attempts
- **Error code matrix** — 400/401/403/404/422/500 for each route
- **Pagination** — first/last/empty/oversized pages
- **File uploads** — valid, oversized, wrong MIME type, empty
- **Rate limiting** — burst detection, per-user vs global limits
---
## When to Use
- New API added — generate test scaffold before writing implementation (TDD)
- Legacy API with no tests — scan and generate baseline coverage
- API contract review — verify existing tests match current route definitions
- Pre-release regression check — ensure all routes have at least smoke tests
- Security audit prep — generate adversarial input tests
---
## Route Detection
### Next.js App Router
```bash
# Find all route handlers
find ./app/api -name "route.ts" -o -name "route.js" | sort
# Extract HTTP methods from each route file
grep -rn "export async function\|export function" app/api/**/route.ts | \
grep -oE "(GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS)" | sort -u
# Full route map
find ./app/api -name "route.ts" | while read f; do
route=$(echo $f | sed 's|./app||' | sed 's|/route.ts||')
methods=$(grep -oE "export (async )?function (GET|POST|PUT|PATCH|DELETE)" "$f" | \
grep -oE "(GET|POST|PUT|PATCH|DELETE)")
echo "$methods $route"
done
```
### Express
```bash
# Find all router files
find ./src -name "*.ts" -o -name "*.js" | xargs grep -l "router\.\(get\|post\|put\|delete\|patch\)" 2>/dev/null
# Extract routes with line numbers
grep -rn "router\.\(get\|post\|put\|delete\|patch\)\|app\.\(get\|post\|put\|delete\|patch\)" \
src/ --include="*.ts" | grep -oE "(get|post|put|delete|patch)\(['\"][^'\"]*['\"]"
# Generate route map
grep -rn "router\.\|app\." src/ --include="*.ts" | \
grep -oE "\.(get|post|put|delete|patch)\(['\"][^'\"]+['\"]" | \
sed "s/\.\(.*\)('\(.*\)'/\U\1 \2/"
```
### FastAPI
```bash
# Find all route decorators
grep -rn "@app\.\|@router\." . --include="*.py" | \
grep -E "@(app|router)\.(get|post|put|delete|patch)"
# Extract with path and function name
grep -rn "@\(app\|router\)\.\(get\|post\|put\|delete\|patch\)" . --include="*.py" | \
grep -oE "@(app|router)\.(get|post|put|delete|patch)\(['\"][^'\"]*['\"]"
```
### Django REST Framework
```bash
# urlpatterns extraction
grep -rn "path\|re_path\|url(" . --include="*.py" | grep "urlpatterns" -A 50 | \
grep -E "path\(['\"]" | grep -oE "['\"][^'\"]+['\"]" | head -40
# ViewSet router registration
grep -rn "router\.register\|DefaultRouter\|SimpleRouter" . --include="*.py"
```
---
## Test Generation Patterns
### Auth Test Matrix
For every authenticated endpoint, generate:
| Test Case | Expected Status |
|-----------|----------------|
| No Authorization header | 401 |
| Invalid token format | 401 |
| Valid token, wrong user role | 403 |
| Expired JWT token | 401 |
| Valid token, correct role | 2xx |
| Token from deleted user | 401 |
### Input Validation Matrix
For every POST/PUT/PATCH endpoint with a request body:
| Test Case | Expected Status |
|-----------|----------------|
| Empty body `{}` | 400 or 422 |
| Missing required fields (one at a time) | 400 or 422 |
| Wrong type (string where int expected) | 400 or 422 |
| Boundary: value at min-1 | 400 or 422 |
| Boundary: value at min | 2xx |
| Boundary: value at max | 2xx |
| Boundary: value at max+1 | 400 or 422 |
| SQL injection in string field | 400 or 200 (sanitized) |
| XSS payload in string field | 400 or 200 (sanitized) |
| Null values for required fields | 400 or 422 |
---
## Example Test Files
→ See references/example-test-files.md for details
## Generating Tests from Route Scan
When given a codebase, follow this process:
1. **Scan routes** using the detection commands above
2. **Read each route handler** to understand:
- Expected request body schema
- Auth requirements (middleware, decorators)
- Return types and status codes
- Business rules (ownership, role checks)
3. **Generate test file** per route group using the patterns above
4. **Name tests descriptively**: `"returns 401 when token is expired"` not `"auth test 3"`
5. **Use factories/fixtures** for test data — never hardcode IDs
6. **Assert response shape**, not just status code
---
## Common Pitfalls
- **Testing only happy paths** — 80% of bugs live in error paths; test those first
- **Hardcoded test data IDs** — use factories/fixtures; IDs change between environments
- **Shared state between tests** — always clean up in afterEach/afterAll
- **Testing implementation, not behavior** — test what the API returns, not how it does it
- **Missing boundary tests** — off-by-one errors are extremely common in pagination and limits
- **Not testing token expiry** — expired tokens behave differently from invalid ones
- **Ignoring Content-Type** — test that API rejects wrong content types (xml when json expected)
---
## Best Practices
1. One describe block per endpoint — keeps failures isolated and readable
2. Seed minimal data — don't load the entire DB; create only what the test needs
3. Use `beforeAll` for shared setup, `afterAll` for cleanup — not `beforeEach` for expensive ops
4. Assert specific error messages/fields, not just status codes
5. Test that sensitive fields (password, secret) are never in responses
6. For auth tests, always test the "missing header" case separately from "invalid token"
7. Add rate limit tests last — they can interfere with other test suites if run in parallel 用户提示词模板
填充变量后发送,即可运行该技能: {{variables}}
变量
| 名称 | 必填 | 说明 | 示例 |
|---|
完整技能配置
标准 .aiskill 文件,提供 JSON 与 YAML 两种格式。
{
"format": "aiskill/v1",
"skill": {
"name": "api-test-suite-builder",
"slug": "api-test-suite-builder",
"version": "1.0.0",
"description": "Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.",
"category": "Development",
"tags": [
"testing",
"api"
],
"platforms": [
"chatgpt",
"claude-code",
"cursor"
],
"tested_environment": "Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and compatible agents",
"license": "MIT"
},
"prompts": {
"system": "# API Test Suite Builder\r\n\r\n**Tier:** POWERFUL\r\n**Category:** Engineering\r\n**Domain:** Testing / API Quality\r\n\r\n---\r\n\r\n## Overview\r\n\r\nScans API route definitions across frameworks (Next.js App Router, Express, FastAPI, Django REST) and\r\nauto-generates comprehensive test suites covering auth, input validation, error codes, pagination, file\r\nuploads, and rate limiting. Outputs ready-to-run test files for Vitest+Supertest (Node) or Pytest+httpx\r\n(Python).\r\n\r\n---\r\n\r\n## Core Capabilities\r\n\r\n- **Route detection** — scan source files to extract all API endpoints\r\n- **Auth coverage** — valid/invalid/expired tokens, missing auth header\r\n- **Input validation** — missing fields, wrong types, boundary values, injection attempts\r\n- **Error code matrix** — 400/401/403/404/422/500 for each route\r\n- **Pagination** — first/last/empty/oversized pages\r\n- **File uploads** — valid, oversized, wrong MIME type, empty\r\n- **Rate limiting** — burst detection, per-user vs global limits\r\n\r\n---\r\n\r\n## When to Use\r\n\r\n- New API added — generate test scaffold before writing implementation (TDD)\r\n- Legacy API with no tests — scan and generate baseline coverage\r\n- API contract review — verify existing tests match current route definitions\r\n- Pre-release regression check — ensure all routes have at least smoke tests\r\n- Security audit prep — generate adversarial input tests\r\n\r\n---\r\n\r\n## Route Detection\r\n\r\n### Next.js App Router\r\n```bash\r\n# Find all route handlers\r\nfind ./app/api -name \"route.ts\" -o -name \"route.js\" | sort\r\n\r\n# Extract HTTP methods from each route file\r\ngrep -rn \"export async function\\|export function\" app/api/**/route.ts | \\\r\n grep -oE \"(GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS)\" | sort -u\r\n\r\n# Full route map\r\nfind ./app/api -name \"route.ts\" | while read f; do\r\n route=$(echo $f | sed 's|./app||' | sed 's|/route.ts||')\r\n methods=$(grep -oE \"export (async )?function (GET|POST|PUT|PATCH|DELETE)\" \"$f\" | \\\r\n grep -oE \"(GET|POST|PUT|PATCH|DELETE)\")\r\n echo \"$methods $route\"\r\ndone\r\n```\r\n\r\n### Express\r\n```bash\r\n# Find all router files\r\nfind ./src -name \"*.ts\" -o -name \"*.js\" | xargs grep -l \"router\\.\\(get\\|post\\|put\\|delete\\|patch\\)\" 2>/dev/null\r\n\r\n# Extract routes with line numbers\r\ngrep -rn \"router\\.\\(get\\|post\\|put\\|delete\\|patch\\)\\|app\\.\\(get\\|post\\|put\\|delete\\|patch\\)\" \\\r\n src/ --include=\"*.ts\" | grep -oE \"(get|post|put|delete|patch)\\(['\\\"][^'\\\"]*['\\\"]\"\r\n\r\n# Generate route map\r\ngrep -rn \"router\\.\\|app\\.\" src/ --include=\"*.ts\" | \\\r\n grep -oE \"\\.(get|post|put|delete|patch)\\(['\\\"][^'\\\"]+['\\\"]\" | \\\r\n sed \"s/\\.\\(.*\\)('\\(.*\\)'/\\U\\1 \\2/\"\r\n```\r\n\r\n### FastAPI\r\n```bash\r\n# Find all route decorators\r\ngrep -rn \"@app\\.\\|@router\\.\" . --include=\"*.py\" | \\\r\n grep -E \"@(app|router)\\.(get|post|put|delete|patch)\"\r\n\r\n# Extract with path and function name\r\ngrep -rn \"@\\(app\\|router\\)\\.\\(get\\|post\\|put\\|delete\\|patch\\)\" . --include=\"*.py\" | \\\r\n grep -oE \"@(app|router)\\.(get|post|put|delete|patch)\\(['\\\"][^'\\\"]*['\\\"]\"\r\n```\r\n\r\n### Django REST Framework\r\n```bash\r\n# urlpatterns extraction\r\ngrep -rn \"path\\|re_path\\|url(\" . --include=\"*.py\" | grep \"urlpatterns\" -A 50 | \\\r\n grep -E \"path\\(['\\\"]\" | grep -oE \"['\\\"][^'\\\"]+['\\\"]\" | head -40\r\n\r\n# ViewSet router registration\r\ngrep -rn \"router\\.register\\|DefaultRouter\\|SimpleRouter\" . --include=\"*.py\"\r\n```\r\n\r\n---\r\n\r\n## Test Generation Patterns\r\n\r\n### Auth Test Matrix\r\n\r\nFor every authenticated endpoint, generate:\r\n\r\n| Test Case | Expected Status |\r\n|-----------|----------------|\r\n| No Authorization header | 401 |\r\n| Invalid token format | 401 |\r\n| Valid token, wrong user role | 403 |\r\n| Expired JWT token | 401 |\r\n| Valid token, correct role | 2xx |\r\n| Token from deleted user | 401 |\r\n\r\n### Input Validation Matrix\r\n\r\nFor every POST/PUT/PATCH endpoint with a request body:\r\n\r\n| Test Case | Expected Status |\r\n|-----------|----------------|\r\n| Empty body `{}` | 400 or 422 |\r\n| Missing required fields (one at a time) | 400 or 422 |\r\n| Wrong type (string where int expected) | 400 or 422 |\r\n| Boundary: value at min-1 | 400 or 422 |\r\n| Boundary: value at min | 2xx |\r\n| Boundary: value at max | 2xx |\r\n| Boundary: value at max+1 | 400 or 422 |\r\n| SQL injection in string field | 400 or 200 (sanitized) |\r\n| XSS payload in string field | 400 or 200 (sanitized) |\r\n| Null values for required fields | 400 or 422 |\r\n\r\n---\r\n\r\n## Example Test Files\r\n→ See references/example-test-files.md for details\r\n\r\n## Generating Tests from Route Scan\r\n\r\nWhen given a codebase, follow this process:\r\n\r\n1. **Scan routes** using the detection commands above\r\n2. **Read each route handler** to understand:\r\n - Expected request body schema\r\n - Auth requirements (middleware, decorators)\r\n - Return types and status codes\r\n - Business rules (ownership, role checks)\r\n3. **Generate test file** per route group using the patterns above\r\n4. **Name tests descriptively**: `\"returns 401 when token is expired\"` not `\"auth test 3\"`\r\n5. **Use factories/fixtures** for test data — never hardcode IDs\r\n6. **Assert response shape**, not just status code\r\n\r\n---\r\n\r\n## Common Pitfalls\r\n\r\n- **Testing only happy paths** — 80% of bugs live in error paths; test those first\r\n- **Hardcoded test data IDs** — use factories/fixtures; IDs change between environments\r\n- **Shared state between tests** — always clean up in afterEach/afterAll\r\n- **Testing implementation, not behavior** — test what the API returns, not how it does it\r\n- **Missing boundary tests** — off-by-one errors are extremely common in pagination and limits\r\n- **Not testing token expiry** — expired tokens behave differently from invalid ones\r\n- **Ignoring Content-Type** — test that API rejects wrong content types (xml when json expected)\r\n\r\n---\r\n\r\n## Best Practices\r\n\r\n1. One describe block per endpoint — keeps failures isolated and readable\r\n2. Seed minimal data — don't load the entire DB; create only what the test needs\r\n3. Use `beforeAll` for shared setup, `afterAll` for cleanup — not `beforeEach` for expensive ops\r\n4. Assert specific error messages/fields, not just status codes\r\n5. Test that sensitive fields (password, secret) are never in responses\r\n6. For auth tests, always test the \"missing header\" case separately from \"invalid token\"\r\n7. Add rate limit tests last — they can interfere with other test suites if run in parallel",
"user_template": ""
},
"variables": [],
"install": {
"steps": [
{
"title": "Download & unzip",
"detail": "Download the .zip package from SkillVault and unzip it. The api-test-suite-builder/ folder contains SKILL.md plus any companion scripts, references and assets."
},
{
"title": "Copy into your agent skills directory",
"detail": "Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session."
},
{
"title": "Use it",
"detail": "Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description."
}
]
},
"usage": {
"steps": []
},
"metadata": {
"author": "SkillVault",
"source": "https://skillvault.top/skills/api-test-suite-builder",
"exported_at": "2026-11-03T07:42:45.158Z"
}
} format: aiskill/v1
skill:
name: api-test-suite-builder
slug: api-test-suite-builder
version: 1.0.0
description: >-
Use when the user asks to generate API tests, create integration test suites, test REST
endpoints, or build contract tests.
category: Development
tags:
- testing
- api
platforms:
- chatgpt
- claude-code
- cursor
tested_environment: >-
Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and
compatible agents
license: MIT
prompts:
system: "# API Test Suite Builder\r\n\r\n**Tier:** POWERFUL\r\n**Category:** Engineering\r\n**Domain:** Testing / API Quality\r\n\r\n---\r\n\r\n## Overview\r\n\r\nScans API route definitions across frameworks (Next.js App Router, Express, FastAPI, Django REST) and\r\nauto-generates comprehensive test suites covering auth, input validation, error codes, pagination, file\r\nuploads, and rate limiting. Outputs ready-to-run test files for Vitest+Supertest (Node) or Pytest+httpx\r\n(Python).\r\n\r\n---\r\n\r\n## Core Capabilities\r\n\r\n- **Route detection** — scan source files to extract all API endpoints\r\n- **Auth coverage** — valid/invalid/expired tokens, missing auth header\r\n- **Input validation** — missing fields, wrong types, boundary values, injection attempts\r\n- **Error code matrix** — 400/401/403/404/422/500 for each route\r\n- **Pagination** — first/last/empty/oversized pages\r\n- **File uploads** — valid, oversized, wrong MIME type, empty\r\n- **Rate limiting** — burst detection, per-user vs global limits\r\n\r\n---\r\n\r\n## When to Use\r\n\r\n- New API added — generate test scaffold before writing implementation (TDD)\r\n- Legacy API with no tests — scan and generate baseline coverage\r\n- API contract review — verify existing tests match current route definitions\r\n- Pre-release regression check — ensure all routes have at least smoke tests\r\n- Security audit prep — generate adversarial input tests\r\n\r\n---\r\n\r\n## Route Detection\r\n\r\n### Next.js App Router\r\n```bash\r\n# Find all route handlers\r\nfind ./app/api -name \"route.ts\" -o -name \"route.js\" | sort\r\n\r\n# Extract HTTP methods from each route file\r\ngrep -rn \"export async function\\|export function\" app/api/**/route.ts | \\\r\n grep -oE \"(GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS)\" | sort -u\r\n\r\n# Full route map\r\nfind ./app/api -name \"route.ts\" | while read f; do\r\n route=$(echo $f | sed 's|./app||' | sed 's|/route.ts||')\r\n methods=$(grep -oE \"export (async )?function (GET|POST|PUT|PATCH|DELETE)\" \"$f\" | \\\r\n grep -oE \"(GET|POST|PUT|PATCH|DELETE)\")\r\n echo \"$methods $route\"\r\ndone\r\n```\r\n\r\n### Express\r\n```bash\r\n# Find all router files\r\nfind ./src -name \"*.ts\" -o -name \"*.js\" | xargs grep -l \"router\\.\\(get\\|post\\|put\\|delete\\|patch\\)\" 2>/dev/null\r\n\r\n# Extract routes with line numbers\r\ngrep -rn \"router\\.\\(get\\|post\\|put\\|delete\\|patch\\)\\|app\\.\\(get\\|post\\|put\\|delete\\|patch\\)\" \\\r\n src/ --include=\"*.ts\" | grep -oE \"(get|post|put|delete|patch)\\(['\\\"][^'\\\"]*['\\\"]\"\r\n\r\n# Generate route map\r\ngrep -rn \"router\\.\\|app\\.\" src/ --include=\"*.ts\" | \\\r\n grep -oE \"\\.(get|post|put|delete|patch)\\(['\\\"][^'\\\"]+['\\\"]\" | \\\r\n sed \"s/\\.\\(.*\\)('\\(.*\\)'/\\U\\1 \\2/\"\r\n```\r\n\r\n### FastAPI\r\n```bash\r\n# Find all route decorators\r\ngrep -rn \"@app\\.\\|@router\\.\" . --include=\"*.py\" | \\\r\n grep -E \"@(app|router)\\.(get|post|put|delete|patch)\"\r\n\r\n# Extract with path and function name\r\ngrep -rn \"@\\(app\\|router\\)\\.\\(get\\|post\\|put\\|delete\\|patch\\)\" . --include=\"*.py\" | \\\r\n grep -oE \"@(app|router)\\.(get|post|put|delete|patch)\\(['\\\"][^'\\\"]*['\\\"]\"\r\n```\r\n\r\n### Django REST Framework\r\n```bash\r\n# urlpatterns extraction\r\ngrep -rn \"path\\|re_path\\|url(\" . --include=\"*.py\" | grep \"urlpatterns\" -A 50 | \\\r\n grep -E \"path\\(['\\\"]\" | grep -oE \"['\\\"][^'\\\"]+['\\\"]\" | head -40\r\n\r\n# ViewSet router registration\r\ngrep -rn \"router\\.register\\|DefaultRouter\\|SimpleRouter\" . --include=\"*.py\"\r\n```\r\n\r\n---\r\n\r\n## Test Generation Patterns\r\n\r\n### Auth Test Matrix\r\n\r\nFor every authenticated endpoint, generate:\r\n\r\n| Test Case | Expected Status |\r\n|-----------|----------------|\r\n| No Authorization header | 401 |\r\n| Invalid token format | 401 |\r\n| Valid token, wrong user role | 403 |\r\n| Expired JWT token | 401 |\r\n| Valid token, correct role | 2xx |\r\n| Token from deleted user | 401 |\r\n\r\n### Input Validation Matrix\r\n\r\nFor every POST/PUT/PATCH endpoint with a request body:\r\n\r\n| Test Case | Expected Status |\r\n|-----------|----------------|\r\n| Empty body `{}` | 400 or 422 |\r\n| Missing required fields (one at a time) | 400 or 422 |\r\n| Wrong type (string where int expected) | 400 or 422 |\r\n| Boundary: value at min-1 | 400 or 422 |\r\n| Boundary: value at min | 2xx |\r\n| Boundary: value at max | 2xx |\r\n| Boundary: value at max+1 | 400 or 422 |\r\n| SQL injection in string field | 400 or 200 (sanitized) |\r\n| XSS payload in string field | 400 or 200 (sanitized) |\r\n| Null values for required fields | 400 or 422 |\r\n\r\n---\r\n\r\n## Example Test Files\r\n→ See references/example-test-files.md for details\r\n\r\n## Generating Tests from Route Scan\r\n\r\nWhen given a codebase, follow this process:\r\n\r\n1. **Scan routes** using the detection commands above\r\n2. **Read each route handler** to understand:\r\n - Expected request body schema\r\n - Auth requirements (middleware, decorators)\r\n - Return types and status codes\r\n - Business rules (ownership, role checks)\r\n3. **Generate test file** per route group using the patterns above\r\n4. **Name tests descriptively**: `\"returns 401 when token is expired\"` not `\"auth test 3\"`\r\n5. **Use factories/fixtures** for test data — never hardcode IDs\r\n6. **Assert response shape**, not just status code\r\n\r\n---\r\n\r\n## Common Pitfalls\r\n\r\n- **Testing only happy paths** — 80% of bugs live in error paths; test those first\r\n- **Hardcoded test data IDs** — use factories/fixtures; IDs change between environments\r\n- **Shared state between tests** — always clean up in afterEach/afterAll\r\n- **Testing implementation, not behavior** — test what the API returns, not how it does it\r\n- **Missing boundary tests** — off-by-one errors are extremely common in pagination and limits\r\n- **Not testing token expiry** — expired tokens behave differently from invalid ones\r\n- **Ignoring Content-Type** — test that API rejects wrong content types (xml when json expected)\r\n\r\n---\r\n\r\n## Best Practices\r\n\r\n1. One describe block per endpoint — keeps failures isolated and readable\r\n2. Seed minimal data — don't load the entire DB; create only what the test needs\r\n3. Use `beforeAll` for shared setup, `afterAll` for cleanup — not `beforeEach` for expensive ops\r\n4. Assert specific error messages/fields, not just status codes\r\n5. Test that sensitive fields (password, secret) are never in responses\r\n6. For auth tests, always test the \"missing header\" case separately from \"invalid token\"\r\n7. Add rate limit tests last — they can interfere with other test suites if run in parallel"
user_template: ""
variables: []
install:
steps:
- title: Download & unzip
detail: >-
Download the .zip package from SkillVault and unzip it. The api-test-suite-builder/ folder
contains SKILL.md plus any companion scripts, references and assets.
- title: Copy into your agent skills directory
detail: >-
Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code),
.codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or
reload the session.
- title: Use it
detail: >-
Describe the task in natural language; the agent loads the skill automatically when the
request matches the skill description.
usage:
steps: []
metadata:
author: SkillVault
source: https://skillvault.top/skills/api-test-suite-builder
exported_at: "2026-11-03T07:42:45.158Z"
安装指南
- 1
Download & unzip
Download the .zip package from SkillVault and unzip it. The api-test-suite-builder/ folder contains SKILL.md plus any companion scripts, references and assets.
- 2
Copy into your agent skills directory
Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session.
- 3
Use it
Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description.
使用方法
平台兼容性
相关技能
security-pen-testing
Use when the user asks to perform security audits, penetration testing, vulnerability scanning, OWASP Top 10 checks, or offensive security assessments. Covers static analysis, dependency scanning, secret detection, API security testing, and pen test report generation.
llm-cost-optimizer
Use proactively whenever LLM API costs come up -- or should. Triggers include: 'my AI costs are too high', 'optimize token usage', 'which model should I use', 'LLM spend is out of control', 'implement prompt caching', 'we're about to launch an AI feature', 'build me an AI endpoint'. Don't wait for an explicit cost complaint -- if someone is building an AI feature, designing an LLM endpoint, or choosing between models, cost architecture belongs in the conversation. Apply immediately when any of these are true: a system prompt appears that exceeds a few hundred tokens, all requests are hitting the same model, max_tokens is not set, or no per-feature cost logging exists. NOT for RAG pipeline design (use rag-architect). NOT for improving prompt quality or effectiveness (use senior-prompt-engineer).
mcp-server-builder
Design and ship production-ready MCP (Model Context Protocol) servers from OpenAPI contracts instead of hand-written tool wrappers. Python and TypeScript support, schema validation, safe evolution. Use when exposing an existing API as an MCP server, building tool integrations for Claude or Codex or Cursor, or scaffolding an MCP project from scratch.