What problem does it solve?
This Skill provides a repeatable, evidence-first process to verify that HTTP APIs behave correctly in real environments by exercising health endpoints, CRUD flows, authentication, pagination, error responses, and rate limits while saving full response artifacts for auditing.
Core Features & Use Cases
- Health checks: Confirm service liveness and expected health payloads before deeper tests.
- CRUD cycle validation: Create, read, update, and delete resources while capturing full JSON responses and IDs for traceability.
- Authentication and authorization checks: Validate token issuance, expired/invalid token handling, and role-based access (401/403).
- Error and pagination testing: Ensure meaningful error bodies for 4xx/5xx responses and verify pagination consistency.
- Evidence capture: Save complete response bodies, HTTP status codes, and headers to an evidence directory for forensic review.
- Use Case: Run this Skill during API changes or deployments to detect contract regressions, auth failures, and pagination bugs while collecting proof for triage.
Quick Start
Run the API validation checklist against your running service to exercise health, CRUD, auth, error handling, and pagination while saving all responses to an evidence folder.
