validating-api-contracts

This skill validates API contracts using consumer-driven testing and OpenAPI validation. It leverages Pact for consumer-driven contract testing, ensuring that API providers adhere to the expectations of their consumers. It also validates APIs against OpenAPI specifications to guarantee compliance and identify breaking changes. Use this skill when the user asks to generate contract tests, validate API responses, check backward compatibility, or validate requests/responses using the terms "contract-test", "ct", "Pact", "OpenAPI validation", or "consumer-driven contract testing".

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill validating-api-contracts

What are skills?

0.94x

Review — 53%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 90%

↓ 0.94x

Agent success when using this skill

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

Setting Up Contract Tests for a Mobile App and User Profile Service

Pact consumer-driven contract test generation

Criteria

Without context

With context

Pact library used

100%

Consumer contract generated

100%

Provider verification test created

100%

Consumer role identified

100%

Provider role identified

100%

Request interaction defined

100%

Response expectations defined

100%

API details specific

100%

Runnable test code

100%

Both sides documented

100%

Without context: $0.4343 · 1m 49s · 22 turns · 23 in / 7,273 out tokens

With context: $0.7803 · 2m 51s · 36 turns · 35 in / 9,430 out tokens

81%

-13%

Validating API Responses Against an OpenAPI Specification

OpenAPI specification validation and discrepancy reporting

Criteria

Without context

With context

OpenAPI validator used

58%

Spec loaded correctly

100%

Discrepancies identified

100%

Violations reported

91%

100%

Specific endpoints checked

100%

Response body validated

100%

Validation report file produced

100%

No false positives on valid responses

100%

36%

Up-to-date spec used

100%

Without context: $0.2815 · 1m 12s · 16 turns · 16 in / 4,962 out tokens

With context: $0.6421 · 2m 17s · 32 turns · 32 in / 8,308 out tokens

90%

-1%

Checking API Compatibility Before a New Release

API backward compatibility and breaking change detection

Criteria

Without context

With context

Breaking changes identified

100%

Non-breaking changes distinguished

83%

100%

Backward compatibility check tool/approach

100%

83%

Specific violations reported

100%

CI/CD integration shown

70%

60%

Exit code or pass/fail signal

100%

Both specs compared

100%

Report file produced

100%

Consumer impact described

55%

Without context: $0.4616 · 1m 56s · 18 turns · 19 in / 8,229 out tokens

With context: $0.6985 · 2m 44s · 29 turns · 910 in / 11,157 out tokens

Evaluated: 4 days ago
Agent: Claude Code
Model: Unknown

Table of Contents

Setting Up Contract Tests for a Mobile App and User Profile Service Validating API Responses Against an OpenAPI Specification Checking API Compatibility Before a New Release

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.