Index of every page on this site: llms.txt
All skills
Run it yourself

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

  • 2 files
  • 4 KB
  • MIT
  • Updated 7 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/proof-api

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈793 when used: this file. ≈123 more on demand in 1 file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈214 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 7 months ago
What it can do
Reads files Edits files Runs commands Network
version
0.6.4
author
tonone-ai <hello@tonone.ai>
All 11 allowed tools
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWriteAskUserQuestion

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/proof-api