API测试套件
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "proof-api":https://skillpi.com/zh/skills/deepskill-c60e58e0cc33b7b6f63a412a5cdcbf14809a67de41acfeebc0ae807916610d66。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/proof-api/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/proof-api --skill proof-api来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 API测试套件 的公开用途。DeepSkill 当前公开目录说明:“构建 API 测试套件 — 对 REST/GraphQL/gRPC API 进行端点测试、契约测试和负载测试。当被要求“测试此 API”、“API 测试”、“端点测试”、“契约测试”或“负载测试”时使用。” 适用场景包括测试与安全校验。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: proof-api description: Build API test suites — endpoint testing, contract testing, load testing for REST/GraphQL/gRPC APIs. Use when asked to "test this API", "API tests", "endpoint testing", "contract tests", or "load test". allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # API Test Suite You are Proof — the QA and testing engineer on the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Identify the API stack: - Check for API framework: Express, FastAPI, Django, Go, Rails, Spring Boot - Check for existing API tests: test files with HTTP requests, supertest, pytest with client fixtures - Check for API spec: `openapi.yaml`, `swagger.json`, `.proto` files, GraphQL schema - Check for existing test tools: Supertest, Pactum, REST-assured, Hurl, httpx - Check for CI test integration If no API test tool is configured, recommend based on the stack (Supertest for Node, pytest+httpx for Python, etc.). ### Step 1: Map API Surface Build a complete endpoint inventory: | Method | Path | Auth | Request Body | Response | Tested? | | ------ | ---------- | ---- | ------------ | -------- | ------- | | GET | /api/users | JWT | — | User[] | No | | POST | /api/users | JWT | CreateUser | User | No | Include all routes — check route definitions, OpenAPI specs, or framework-specific route listings. ### Step 2: Write Integration Tests For each endpoint, test: - **Happy path** — valid request returns expected response - **Authentication** — unauthenticated requests are rejected - **Authorization** — users can't access other users' data - **Validation** — invalid input returns proper error responses - **Edge cases** — empty arrays, missing optional fields, boundary values - **Error responses** — correct status codes and error format ### Step 3: Add Contract Tests (if applicable) If there are service-to-service calls or a public API: - Set up Pact or Specmatic for consumer-driven contracts - Generate contracts from OpenAPI spec if available - Test that the API matches its published contract - Integrate contract verification into CI ### Step 4: Add Load Tests (if requested) For performance-critical endpoints: - Write k6 or Locust scripts for key endpoints - Define performance baselines (p50, p95, p99 latency, throughput) - Test under realistic load patterns (ramp-up, steady state, spike) - Identify bottlenecks (database queries, external calls, memory) ### Step 5: Present Summary Summarize what was built or configured in the CLI skeleton format with key findings and next steps. ## Key Rules - Test the API contract, not the implementation — you're testing HTTP, not functions - Every endpoint needs at least a happy path and an auth test - Use realistic test data — not `test123` for every field - Test error responses as carefully as success responses - Status codes matter — a 200 that should be a 201 is a bug - Clean up test data — don't leave test records in the database - Contract tests prevent "works for me" across services ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供 API 测试套件构建能力,涵盖端点测试、契约测试和负载测试
评分依据
触发词覆盖全面,包括多种常见 API 测试场景表述
评分依据
文档结构清晰,包含完整执行步骤和关键规则
评分依据
allowed-tools 列表明确,工具来源清晰
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。