Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

API Tester

Generates and verifies API tests strictly from real OpenAPI specs, route code and existing tests, keeping test generation separate from executing live requests.

Dev & CodingIntermediate★ 868⑂ 95AI score 8/10Last updated: Sep 22, 2026

What it does

  • Reads OpenAPI/Swagger files, routes, controllers, DTOs, validators and existing tests to establish the actual API contract.
  • Builds a contract matrix per endpoint: method/path, auth & permissions, request constraints, declared responses, side effects/idempotency, and test environment plus cleanup strategy.
  • Flags mismatches between spec, implementation and existing tests, and asks for confirmation instead of freezing a guess into a new test.
  • Never assumes 400/401/403/404/500 exist by convention — assertions only for status codes declared in the contract or actually reachable in code.
  • Separates "generate tests" from "send requests": production, shared staging, paid APIs and any write operation require explicit authorization.
  • Uses the repo's own test/lint scripts and lockfile-pinned tooling instead of bare npx or globally installed utilities; parses YAML/JSON with real parsers, not grep.
  • Reports with a fixed template covering cases, evidence, executed commands, exit status, cleanup and unresolved contract questions.

Who it's for

  • Backend developers filling gaps in integration and regression coverage.
  • QA and platform engineers validating that OpenAPI specs match real behaviour.
  • Teams burned by AI-written tests that assert response fields which don't exist.

Examples

  1. "Add integration tests for /orders" → reads routes and DTOs, builds the contract matrix, then writes happy-path, boundary and permission cases only for constraints that genuinely exist.
  2. "Check whether our OpenAPI spec matches the implementation" → diffs spec against handlers, lists inconsistencies and asks which side is authoritative.
  3. "Run these tests against staging" → first confirms base URL, credentials, whether write requests are allowed and how data gets cleaned up, then runs the minimal target suite and reports command, exit code and any leftover data.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/laolaoshiren/claude-code-skills-zh/HEAD/skills/api-tester/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/api-tester folder from the GitHub repo laolaoshiren/claude-code-skills-zh into my ~/.claude/skills/api-tester/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/laolaoshiren/claude-code-skills-zh.git /tmp/ccs-zh && mkdir -p ~/.claude/skills && cp -r /tmp/ccs-zh/skills/api-tester ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repository: git clone https://github.com/laolaoshiren/claude-code-skills-zh.git
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r claude-code-skills-zh/skills/api-tester ~/.claude/skills/
  5. Verify that ~/.claude/skills/api-tester/SKILL.md exists.
  6. Restart Claude Code and try a prompt such as "Write integration tests for this project's API".
  7. If you want live requests executed, state the target environment (local/test/staging) and whether write operations are permitted.
View source on GitHub ↗License: MIT