QA API Testing Contracts
API testing and contract validation. Design and execute schema validation, contract tests, negative testing, and change safety for REST, GraphQL, and gRPC APIs. Use when you need API test plans, contract testing, or CI quality gates.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill qa-api-testing-contractsgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/qa-api-testing-contracts ~/.claude/skills/qa-api-testing-contractsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# QA API Testing and Contracts ## When to Use This Skill Use this skill when you need to: - Design API test plans for REST, GraphQL, or gRPC services. - Implement contract testing with Pact or consumer-driven workflows. - Set up schema validation in CI/CD pipelines. - Review API changes for backward compatibility. - Define quality gates for API releases. ## Scope - Validate API schemas and enforce contracts. - Design functional, negative, and edge case tests. - Plan mocking and consumer driven contracts. - Define CI gates and release safety checks. - Align API tests with SLOs and error budgets. ## Ask For Inputs - API type (REST, GraphQL, gRPC) and schemas (OpenAPI, SDL, proto). - Environments and authentication methods. - Critical endpoints and business flows. - Data constraints, idempotency, and rate limits. - Change cadence and backward compatibility policy. - Current test tooling and CI pipeline. ## Workflow 1. Confirm API surface and schema sources. 2. Establish contract rules (breaking vs non breaking). 3. Generate schema validation tests. 4. Create functional tests for happy paths. 5. Add negative, boundary, and auth tests. 6. Add consumer contract tests or mocks as needed. 7. Define CI gates, reporting, and rollback triggers. ## Outputs - API test plan and coverage map by endpoint. - Contract validation suite and schema checks. - Negative and security test list. - Mock and test data strategy. - CI quality gates and release checklist. ## Quality Checks
Details
- Skill name
qa-api-testing-contracts- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/qa-api-testing-contracts/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the QA API Testing Contracts skill do?
API testing and contract validation. Design and execute schema validation, contract tests, negative testing, and change safety for REST, GraphQL, and gRPC APIs. Use when you need API test plans, contract testing, or CI quality gates.
How do I install the QA API Testing Contracts skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is QA API Testing Contracts popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
QA Handoff
5vnovakovits/claude-skills
Update a ticket with what shipped and tell QA what to test, in lean, empathetic, user-journey language. Verifies what is actually merged, released and deployed, maps each change to the ticket it fixes, writes a short status (in production / open / left, by owner) and a numbered list of user journeys to test with expected outcomes and what to report. Use when a change is merged or deployed and someone asks "what should QA test", "update the ticket", "post what we merged", "is this live", or wants a tester note, release note or status comment for any tracker (Linear, Jira, GitHub Issues).
QA Agent Testing
8Freddy-CHEN-ux/00_claude_skills
QA harness for agentic systems: scenario suites, determinism controls, tool sandboxing, scoring rubrics, and regression protocols covering success, safety, latency, and cost.
QA Observability
8Freddy-CHEN-ux/00_claude_skills
Observability for quality engineering: using logs, metrics, and traces as test signals; SLI/SLO quality gates; trace-based debugging of failures; and cost-aware instrumentation with OpenTelemetry.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.