Individual skill
api-testing-checklist
A fast, ordered methodology for assessing an API end to end — REST/GraphQL/gRPC/SOAP — so nothing gets skipped. Load when the target is an API (or recon found one), on "test this API", "checklist", methodology triage, or to confirm coverage before reporting. Signals: /api, swagger/openapi.json, GraphQL /graphql, gRPC, JSON/XML endpoints, a mobile/SPA backend.
skills/api/api-testing-checklist/SKILL.md
Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Oct 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-security Repository topic
- application-security Repository topic
- blue-team Repository topic
- bug-bounty Repository topic
- claude-code Repository topic
- codex Repository topic
- detection-engineering Repository topic
- gemini Repository topic
- testing Derived category
- docs Derived category
- docs-api Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,786 bytes
Read excerpt
# API testing methodology (work top to bottom)
Confirm scope first (`tradecraft-scope-roe`). Each phase links to the skill that goes deep — load it,
work its `cheatsheet.md` where present, and don't mark a phase `failed` until you've covered it
(house rule: fuzz every input/context/encoding, blind/OOB). This is your coverage map.
## 1 · Discover & map the surface
- [ ] Find the API: `/api`, subdomains, JS files (`recon-js-analysis`), mobile/SPA traffic (`recon-content-discovery`)
- [ ] Grab the spec: `swagger.json` / `openapi.json` / GraphQL introspection / `.proto` — enumerate every endpoint, method, param
- [ ] Note auth model (Bearer/JWT/API key/cookie/mTLS), versions (`/v1`,`/v2`), and content types
- [ ] Map roles: create **two accounts** (and an unauth client) — you need them for access-control tests
## 2 · Authentication
- [ ] Token flaws — JWT alg/kid/key confusion (`web-auth-jwt`), API-key leakage/predictability