tonone-ai/tonone / bundle/engineering-team/skills/proof-api
proof-api
VerifiedBuild 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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
SKILL.md
View on GitHub---
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
compatibility: Designed for Claude Code
tags: [engineering, qa, testing, api]
---
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
# 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |