Agent skill

Testing Integration

by yonatangross in yonatangross/orchestkit

Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation.

MITAuto-check passedTesting & QA

Install Testing Integration

skills CLI
$ npx skills add yonatangross/orchestkit --skill testing-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install yonatangross/orchestkit testing-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/testing-integration .claude/skills/testing-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
testing-integration
GitHub stars
288
Token cost
~2.7k tokens
SKILL.md length
687 words
Files
19 (incl. scripts, references)
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation.

  • Works in 6 steps: Test at boundaries -- API inputs,… → Fresh state per test -- In-memory… → Use matchers in contracts -- Like(),… → …
  • Testing API boundaries
  • SKILL.md covers Quick Reference, Upstream coverage (do not…, Stateful API Testing (emulate… and Testcontainers (real…, plus 5 more sections
  • Verifying contracts

What it does

Testing Integration is an agent skill from yonatangross/orchestkit. Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.

Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 22 other files, including scripts and reference files (for example `checklists/contract-testing-checklist.md`, `checklists/property-testing-checklist.md` and `examples/orchestkit-test-strategy.md`). Compatibility notes: Claude Code 2.1.277+.

It sits in Testing & QA, covering Integration testing and REST APIs. It works with Zod. The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.

When your agent uses it

  • Testing API boundaries
  • Verifying contracts
  • Validating cross-service integration

Example prompts

  • “/testing-integration”

Requirements

  • Python 3
  • Node.js
  • Docker
  • Compatibility (from SKILL.md): Claude Code 2.1.277+.
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, WebSearch

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Test at boundaries -- API inputs, database queries, service calls, external integrations
  2. Fresh state per test -- In-memory databases, transaction rollback, no shared mutable state
  3. Use matchers in contracts -- Like(), EachLike(), Term() instead of exact values
  4. Property-based for invariants -- Roundtrip, idempotence, commutativity properties
  5. Validate schemas at edges -- Zod .safeParse() at every API boundary
  6. Evidence-backed completion -- Exit code 0, coverage reports, timestamps

What it can do on your machine

Read from SKILL.md and the folder at commit 1f8d8f3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • WebSearch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.pact.io
    • docs.github.com
    • fastapi.tiangolo.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Claude Code 2.1.277+.

    From compatibility in the SKILL.md frontmatter.

Context cost

Testing Integration loads about 2.7k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 687 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~75
When it runs · the whole SKILL.md, loaded when a task matches
~2.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 1f8d8f3, republished under its MIT licence (© yonatangross). 687 words, ~2,674 tokens.

Download SKILL.mdSave it as .claude/skills/testing-integration/SKILL.md (or your agent's skills folder). This skill also uses 18 other files; get the full folder from GitHub.
name
testing-integration
description
Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Use when testing API boundaries, verifying contracts, or validating cross-service integration.
allowed-tools
Read, Glob, Grep, WebFetch, WebSearch
compatibility
Claude Code 2.1.277+.
license
MIT
context
fork
agent
test-generator
user-invocable
false
disable-model-invocation
false
metadata.category
document-asset-creation
metadata.version
2.1.0
metadata.author
OrchestKit
metadata.complexity
medium
metadata.tags
testing, integration, contract, pact, property, zod, api

Integration & Contract Testing

Focused patterns for testing API boundaries, cross-service contracts, component integration, database layers, property-based verification, and schema validation.

Quick Reference

For complex emulate setups (full config generation, webhook HMAC, CI per-worker port isolation), delegate to the emulate-engineer subagent. Pairs with the emulate-seed skill.

AreaRule / ReferenceImpact
Stateful API testing (emulate)rules/emulate-stateful-testing.mdHIGH
API endpoint testsrules/integration-api.mdHIGH
React component integrationrules/integration-component.mdHIGH
Database layer testingrules/integration-database.mdHIGH
Zod schema validationrules/validation-zod-schema.mdHIGH
Pact contract testingrules/verification-contract.mdMEDIUM
Stateful testing (Hypothesis)rules/verification-stateful.mdMEDIUM
Evidence & property-basedrules/verification-techniques.mdMEDIUM
References
TopicFile
House rules not documented upstreamreferences/ork-delta.md
Consumer-side Pact testsreferences/consumer-tests.md
Hypothesis strategies guidereferences/strategies-guide.md
Checklists
ChecklistFile
Contract testing readinesschecklists/contract-testing-checklist.md
Property-based testingchecklists/property-testing-checklist.md
Scripts & Templates
ScriptFile
Create integration testscripts/create-integration-test.md
Examples
ExampleFile
Full testing strategyexamples/orchestkit-test-strategy.md

Upstream coverage (do not restate)

This skill wraps Pact, the Pact Broker, and FastAPI testing. It carries only the OrchestKit delta. Fetch the vendor docs for the topics below instead of restating them here.

TopicFirst-party source
Pact Broker publish CLI, pact versioning and tagging flagshttps://docs.pact.io/pact_broker/publishing_and_retrieving_pacts
can-i-deploy, record-deployment, record-releasehttps://docs.pact.io/pact_broker/can_i_deploy
Deployment and release recording semanticshttps://docs.pact.io/pact_broker/recording_deployments_and_releases
Broker webhooks that trigger a provider build on contract changehttps://docs.pact.io/pact_broker/webhooks
Consumer version selector syntax (mainBranch, deployedOrReleased, matchingBranch)https://docs.pact.io/pact_broker/advanced_topics/consumer_version_selectors
Pending pact semanticshttps://docs.pact.io/pact_broker/advanced_topics/pending_pacts
Provider state setup hooks and state endpoint wiringhttps://docs.pact.io/getting_started/provider_states
FastAPI TestClient and dependency_overrides for a test databasehttps://fastapi.tiangolo.com/advanced/testing-dependencies/
GitHub Actions job ordering (needs:) and branch filtershttps://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions
QA test-plan paperwork (schedule, roles, defect lifecycle, sign-off tables)Tracker-owned; no single vendor page covers all four. Defect lifecycle: https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues . Schedule, roles and sign-off are org process, not a documented product feature. House quality budgets from the retired template survive in references/ork-delta.md

The house subset of those topics stays in this skill and is not routed away: rules/verification-contract.md keeps the two broker commands ork gates on plus the selector defaults; checklists/contract-testing-checklist.md keeps the CI/CD, isolation and security checkboxes; references/consumer-tests.md keeps the business-language provider-state naming convention and the matcher table. The rules that have no upstream home at all live in references/ork-delta.md.


Stateful API Testing (emulate — FIRST CHOICE)

For GitHub, Vercel, and Google API integration tests, emulate is the first choice. It provides full state machines that model real API behavior — not static mocks.

ToolBest For
emulateStateful API tests (GitHub/Vercel/Google) — FIRST CHOICE
PactCross-team contract verification
MSWFrontend HTTP mocking (simple request/response)
NockNode.js unit-level HTTP interception

See rules/emulate-stateful-testing.md for the full decision matrix, seed-start-test-assert pattern, and incorrect/correct examples.


Show full SKILL.md (279 more words)Show less

Testcontainers (real dependencies in CI)

When contract tests and emulate aren't enough — e.g. testing against real Postgres, Redis, Kafka, or an S3-compatible store — Testcontainers spins up ephemeral Docker containers per test and tears them down afterward. path_patterns above already matches **/testcontainers/**; use these patterns there.

Target: testcontainers >= 11.0.0 (Node) — v11 (Q1 2026) added named-network auto-cleanup, reusable containers via .withReuse(), and first-class Podman support.

Node.js (testcontainers-node)
typescript
import { PostgreSqlContainer } from '@testcontainers/postgresql'
import { describe, beforeAll, afterAll, test, expect } from 'vitest'

describe('UserRepository integration', () => {
  let container: Awaited<ReturnType<PostgreSqlContainer['start']>>
  let repo: UserRepository

  beforeAll(async () => {
    container = await new PostgreSqlContainer('postgres:16-alpine')
      .withDatabase('test')
      .withUsername('test')
      .withPassword('test')
      .withReuse()  // v11+ — reuse across runs to speed CI
      .start()

    repo = new UserRepository(container.getConnectionUri())
    await repo.migrate()
  }, 30_000)

  afterAll(async () => {
    await container.stop()
  })

  test('persists and retrieves a user', async () => {
    const created = await repo.create({ email: 'a@b.c' })
    const found = await repo.findById(created.id)
    expect(found?.email).toBe('a@b.c')
  })
})
Python (testcontainers-python)
python
from testcontainers.postgres import PostgresContainer
import pytest

@pytest.fixture(scope="session")
def postgres():
    with PostgresContainer("postgres:16-alpine") as pg:
        yield pg.get_connection_url()

def test_user_repo(postgres):
    repo = UserRepository(postgres)
    repo.migrate()
    user = repo.create(email="a@b.c")
    assert repo.find_by_id(user.id).email == "a@b.c"

Decision matrix:

ScenarioPick
Third-party API (GitHub, Vercel, Google)emulate
Cross-team API contractPact
Real Postgres / Redis / Kafka integrationTestcontainers
Just mocking HTTP in a frontend testMSW

Quick Start: API Integration Test

TypeScript (Supertest)
typescript
import request from 'supertest';
import { app } from '../app';

describe('POST /api/users', () => {
  test('creates user and returns 201', async () => {
    const response = await request(app)
      .post('/api/users')
      .send({ email: 'test@example.com', name: 'Test' });

    expect(response.status).toBe(201);
    expect(response.body.id).toBeDefined();
    expect(response.body.email).toBe('test@example.com');
  });

  test('returns 400 for invalid email', async () => {
    const response = await request(app)
      .post('/api/users')
      .send({ email: 'invalid', name: 'Test' });

    expect(response.status).toBe(400);
    expect(response.body.error).toContain('email');
  });
});
Python (FastAPI + httpx)
python
import pytest
from httpx import ASGITransport, AsyncClient
from app.main import app

@pytest.fixture
async def client():
    async with AsyncClient(transport=ASGITransport(app=app), base_url="http://test") as ac:
        yield ac

@pytest.mark.asyncio
async def test_create_user(client: AsyncClient):
    response = await client.post(
        "/api/users",
        json={"email": "test@example.com", "name": "Test"}
    )
    assert response.status_code == 201
    assert response.json()["email"] == "test@example.com"

Coverage Targets

AreaTarget
API endpoints70%+
Service layer80%+
Component interactions70%+
Contract testsAll consumer-used endpoints
Property testsAll encode/decode, idempotent functions

Key Principles

  1. Test at boundaries -- API inputs, database queries, service calls, external integrations
  2. Fresh state per test -- In-memory databases, transaction rollback, no shared mutable state
  3. Use matchers in contracts -- Like(), EachLike(), Term() instead of exact values
  4. Property-based for invariants -- Roundtrip, idempotence, commutativity properties
  5. Validate schemas at edges -- Zod .safeParse() at every API boundary
  6. Evidence-backed completion -- Exit code 0, coverage reports, timestamps

When to Use This Skill

  • Writing API endpoint tests (Supertest, httpx)
  • Setting up React component integration tests with providers
  • Creating database integration tests with isolation
  • Implementing Pact consumer/provider contract tests
  • Adding property-based tests with Hypothesis
  • Validating Zod schemas at API boundaries
  • Planning a testing strategy for a new feature or service
  • ork:testing-unit — Unit testing patterns, fixtures, mocking
  • ork:testing-e2e — End-to-end Playwright tests
  • ork:emulate-seed — Seed configuration authoring for emulate providers
  • ork:database-patterns — Database schema and migration patterns
  • ork:api-design — API design patterns for endpoint testing

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 18 other files (scripts, references) in src/skills/testing-integration of yonatangross/orchestkit.

  • SKILL.md
  • checklists/contract-testing-checklist.md
  • checklists/property-testing-checklist.md
  • examples/orchestkit-test-strategy.md
  • references/consumer-tests.md
  • references/ork-delta.md
  • references/strategies-guide.md
  • rules/_sections.md
  • rules/emulate-stateful-testing.md
  • rules/integration-api.md
  • rules/integration-component.md
  • rules/integration-database.md
  • rules/validation-zod-schema.md
  • rules/verification-contract.md
  • rules/verification-stateful.md
  • rules/verification-techniques.md
  • scripts
  • … and 2 more

Open the folder on GitHubat commit 1f8d8f3

Compare with similar skills

Testing Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Testing Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Testing Integration this skillyonatangross/orchestkit288—~2.7kAutomated safety check: PassMIT
API Testingpetrkindlmann/qa-skills163—~2.7kAutomated safety check: PassMIT
Hybrid Cloud Test Gengetsentry/sentry45k—~2.6kAutomated safety check: PassCustom licence
Rust API Test Harnesshashgraph-online/awesome-codex-plugins1.2k—~1.7kAutomated safety check: PassMIT
API Testing RESTPramodDutta/qaskills232—~4.9kAutomated safety check: PassMIT
API Test Suite Builderalirezarezvani/claude-skills28k1 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • API Testing

    petrkindlmann/qa-skills

    Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients.

    163 GitHub stars~2.7k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Hybrid Cloud Test Gen

    getsentry/sentry

    Official

    Generate hybrid cloud tests for the Sentry codebase. An agent skill from getsentry/sentry.

    45k GitHub stars~2.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.2k GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • API Testing REST

    PramodDutta/qaskills

    Comprehensive RESTful API testing patterns covering HTTP methods, status codes, request/response validation, authentication, error handling, and contract testing.

    232 GitHub stars~4.9k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • API Test Suite Builder

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    Testing & QAAuto-check passed
  • OpenAPI to MCP Server

    mcp-use/mcp-use

    Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.

    11k GitHub stars~5.2k tokensUpdated today
    Backend & APIsAuto-check passed

More from yonatangross/orchestkit

All 107 skills in this repo
  • API Design

    yonatangross/orchestkit

    API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.

    288 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Architecture Decision Record

    yonatangross/orchestkit

    ADR templates in the Nygard format with context, decision, consequences, and alternatives.

    288 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Audit Full

    yonatangross/orchestkit

    Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.

    288 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check: notes
  • Code Review Playbook

    yonatangross/orchestkit

    Structured review processes, conventional comments, language-specific checklists, and feedback templates.

    288 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Create PR

    yonatangross/orchestkit

    Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.

    288 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check: notes
  • Explore

    yonatangross/orchestkit

    Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.

    288 GitHub stars~3.9k tokensUpdated yesterday
    Auto-check: notes

Works with

Questions about Testing Integration

What does Testing Integration do?

Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation. Testing Integration is an agent skill from yonatangross/orchestkit. Integration and contract testing patterns — API endpoint tests, component integration, database testing, Pact contract verification, property-based testing, and Zod schema validation.

When should I use Testing Integration?

Testing Integration fits situations like: testing API boundaries; verifying contracts; validating cross-service integration.

How do I install Testing Integration in Claude Code?

Run `npx skills add yonatangross/orchestkit --skill testing-integration -a claude-code`. Or copy the skill folder (src/skills/testing-integration in yonatangross/orchestkit) into .claude/skills/testing-integration in your project. Claude Code loads it when a task matches its description.

How do I install Testing Integration in Codex?

Run `npx skills add yonatangross/orchestkit --skill testing-integration -a codex`. Or copy the skill folder (src/skills/testing-integration in yonatangross/orchestkit) into .agents/skills/testing-integration in your project. Codex loads it when a task matches its description.

Can I use Testing Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yonatangross/orchestkit --skill testing-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-integration, .gemini/skills/testing-integration, .github/skills/testing-integration and .opencode/skills/testing-integration in your project.

What does Testing Integration need to run?

SKILL.md names no scripts, command-line tools or credentials: Testing Integration is instructions for the agent only. Our summary lists: Python 3; Node.js; Docker. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, WebSearch. Compatibility (from SKILL.md): Claude Code 2.1.277+..

Does Testing Integration access the network?

SKILL.md names 3 domains. As links in the text: docs.pact.io, docs.github.com and fastapi.tiangolo.com. This is read from the text; nothing was executed.

Is Testing Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Testing Integration use?

Testing Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Testing Integration use?

About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.

What are the alternatives to Testing Integration?

Skills that share tags, products or a category with Testing Integration: API Testing (petrkindlmann/qa-skills, 163 stars), Hybrid Cloud Test Gen (getsentry/sentry, 45k stars), Rust API Test Harness (hashgraph-online/awesome-codex-plugins, 1.2k stars) and API Testing REST (PramodDutta/qaskills, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Testing Integration?

yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 288 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on October 6, 2026.

Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.