Api Test Suite Builder

Community

borghei

api-test-suite-builder

Generate API test suites from route definitions across frameworks: auth, input validation, contract, k6 load testing, mocking, and OpenAPI-driven generation. Use when adding new APIs, auditing test coverage, or building regression suites.

Overview

Publisher	borghei
Repository	`Claude-Skills`
Skill name	`api-test-suite-builder`
Stars	856
Forks	154
Bundled files	6
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
6 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by borghei on GitHub. Read the source before you install it.

Installation

Install the Api Test Suite Builder AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/borghei/Claude-Skills/tree/main/engineering/api-test-suite-builder
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p .claude/skills
cp -r /tmp/Claude-Skills/engineering/api-test-suite-builder .claude/skills/api-test-suite-builder

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Api Test Suite Builder in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Api Test Suite Builder on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Api Test Suite Builder is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

API Test Suite Builder

Scan API route definitions across frameworks (Next.js App Router, Express, FastAPI, Django REST, Go net/http), analyze request/response schemas, and generate comprehensive test suites covering authentication, authorization, input validation, error handling, pagination, file uploads, rate limiting, contract testing, and load testing. Outputs ready-to-run test files for Vitest+Supertest (Node), Pytest+httpx (Python), or k6 (load testing).

Core Capabilities

Route detection & analysis — scan source files to extract endpoints, parse request/response schemas, detect auth middleware and authorization rules across Node, Python, and Go frameworks.
Test matrix generation — auth (valid/invalid/expired tokens, wrong roles), input validation (missing/wrong-type/boundary/injection), error paths (400/401/403/404/409/422/429/500), pagination, file uploads, and rate limiting.
Contract testing — OpenAPI-to-test generation, Pact consumer-driven contracts, schema snapshot testing for breaking-change detection.
Load testing — k6 scripts with ramp-up patterns and SLA thresholds, latency percentile tracking (P50/P95/P99), concurrent user simulation.

When to Use

New API added — generate a test scaffold before implementation (TDD).
Legacy API with no tests — scan and generate baseline coverage.
Pre-release — ensure all routes have at least smoke tests.
API contract change — detect and test breaking changes.
Security audit — generate adversarial input tests.
Performance validation — create load-test baselines.

Clarify First

Before generating the suite, confirm these inputs. If any is unknown or vague, ASK — do not assume:

Target framework — Vitest+Supertest, Pytest+httpx, or k6 (determines the emitted test-file format via --framework)
Spec or routes source — an OpenAPI spec or the source files to scan (the input the generator parses)
Test scope — auth, input validation, contract, load, or the full matrix (which test categories get generated)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

Tool	Purpose	Command
`test_generator.py`	Generate API test skeletons from an OpenAPI/Swagger spec	`python scripts/test_generator.py spec.json --framework vitest --output tests/`
`coverage_analyzer.py`	Compare spec endpoints vs existing test files to find gaps	`python scripts/coverage_analyzer.py spec.json tests/ --threshold 95`
`contract_validator.py`	Validate response samples against OpenAPI schema contracts	`python scripts/contract_validator.py spec.json samples/ --strict`

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

references/route-detection-and-matrices.md — per-framework route-detection shell commands and the full auth / input-validation / pagination test matrices with worked TypeScript examples. Read when scanning a codebase or writing the core test cases.
references/contract-and-load-testing.md — complete Pact consumer-driven contract test and k6 load-test scripts, plus the commands to run load tests locally, against staging, and in the cloud. Read when adding contract or performance tests.
references/workflow-and-quality.md — the 9-step generation workflow, reusable test-helper patterns (auth, authed request, factories), common pitfalls, best practices, a troubleshooting table, and the success-criteria bar. Read before generating a suite and before shipping it.

Scope & Limitations

This skill covers:

Generating test suites from route definitions for REST APIs across Node.js, Python, and Go frameworks
Authentication, authorization, input validation, pagination, and error-path test generation
Consumer-driven contract testing with Pact and schema snapshot validation
Load and performance testing script generation with k6 and Artillery

This skill does NOT cover:

GraphQL API testing (see engineering/api-design-reviewer for schema review patterns)
End-to-end browser testing or UI interaction testing (see engineering/playwright-pro)
Database migration testing or schema validation (see engineering/database-schema-designer)
Security penetration testing beyond input sanitization checks (see engineering/skill-security-auditor)

Integration Points

Skill	Integration	Data Flow
`engineering/api-design-reviewer`	Validate API design before generating tests	Design review output defines the endpoint contracts that this skill generates tests for
`engineering/ci-cd-pipeline-builder`	Embed generated tests into CI/CD pipelines	Generated test files and k6 scripts are added as pipeline stages with pass/fail gates
`engineering/playwright-pro`	Complement API tests with E2E browser tests	API test suite validates backend behavior; Playwright tests validate the frontend consuming those APIs
`engineering/database-schema-designer`	Align test fixtures with database schema	Schema definitions inform factory functions and seed data used in generated test helpers
`engineering/observability-designer`	Monitor test-covered endpoints in production	Load test thresholds (P95, P99) feed into alerting rules for the same endpoints in production dashboards
`engineering/performance-profiler`	Investigate endpoints that fail load test thresholds	k6 results identify slow endpoints; the profiler skill traces root causes at the code level

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Api Test Suite Builder AI skill do?

Why use Api Test Suite Builder on TypingMind?

Because you install it once and use it with any model. Api Test Suite Builder is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Api Test Suite Builder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/borghei/Claude-Skills/tree/main/engineering/api-test-suite-builder. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Api Test Suite Builder?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Api Test Suite Builder?

As many as you like. As long as a model supports skills, you can use Api Test Suite Builder with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Api Test Suite Builder AI skill free?

It is published on GitHub by borghei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Solid

openclaw

OrganizationPopular

Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and…

Auto Qa

Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

Autoreview

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

API Test Suite Builder

Core Capabilities

When to Use

Clarify First

Tools

References

Scope & Limitations

Integration Points

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now