# Jeremylongshore Claude Code Plugins Plus Skills Contract Test Validator > Overview - Skill: `tomevault-io/jeremylongshore-claude-code-plugins-plus-skills-contract-2` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/jeremylongshore-claude-code-plugins-plus-skills-contract-2` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/jeremylongshore-claude-code-plugins-plus-skills-contract-2/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/jeremylongshore-claude-code-plugins-plus-skills-contract-2 --- ## Overview This skill enables Claude to generate and validate API contracts, ensuring compatibility between API providers and consumers. It uses Pact for consumer-driven contract testing and OpenAPI validation for specification compliance. ## How It Works 1. **Generating Contract Tests**: Claude creates Pact consumer tests based on API usage, generating provider verification tests and building OpenAPI contract validators. 2. **Validating Contracts**: The skill verifies if API responses match the defined contracts. 3. **Checking Compatibility**: It checks for backward compatibility to identify breaking changes in the API. ## When to Use This Skill This skill activates when you need to: - Generate contract tests for an API. - Validate API responses against existing contracts. - Identify breaking changes in an API. ## Examples ### Example 1: Generating Pact Contracts User request: "Generate contract tests for my API using Pact." The skill will: 1. Analyze the API and generate Pact consumer contracts. 2. Create provider verification tests based on the contracts. ### Example 2: Validating an OpenAPI Specification User request: "Validate my API against the OpenAPI specification." The skill will: 1. Validate the API against the provided OpenAPI specification. 2. Report any discrepancies or violations of the specification. ## Best Practices - **Clarity**: Be specific when requesting contract generation or validation, providing relevant API details. - **Completeness**: Ensure that your OpenAPI specifications are up-to-date for accurate validation. - **Context**: Provide context about the consumer and provider roles when using Pact. ## Integration This skill can be integrated with other testing and deployment tools in the Claude Code ecosystem to automate contract verification as part of a CI/CD pipeline. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/jeremylongshore) — claim your Tome and manage your conversions.