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-contracts68
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/skillEvaluation — 90%
↓ 0.94xAgent success when using this skill
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes comprehensive trigger terms with both full names and abbreviations, explicitly states when to use the skill, and carves out a distinct niche in API contract testing that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'validates API contracts', 'consumer-driven testing', 'OpenAPI validation', 'leverages Pact', 'ensuring API providers adhere to expectations', 'validates APIs against OpenAPI specifications', 'identify breaking changes'. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what (validates API contracts using Pact and OpenAPI, checks compliance, identifies breaking changes) AND when with explicit 'Use this skill when...' clause listing specific trigger scenarios and terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'contract tests', 'validate API responses', 'check backward compatibility', 'contract-test', 'ct', 'Pact', 'OpenAPI validation', 'consumer-driven contract testing'. Includes both full terms and abbreviations. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on API contract testing with distinct triggers like 'Pact', 'contract-test', 'ct', 'OpenAPI validation'. Unlikely to conflict with general API testing or documentation skills due to specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content describes what contract testing is and when to use it, but fails to provide any actionable guidance. It lacks executable code examples, specific commands, concrete Pact test templates, or OpenAPI validation scripts. The content tells Claude about the skill rather than teaching Claude how to perform the tasks.
Suggestions
Add executable Pact consumer test code examples showing actual JavaScript/Python test structure with expectations and matchers
Include concrete OpenAPI validation commands (e.g., using spectral, openapi-diff, or similar tools) with example output
Provide a copy-paste ready workflow with specific file paths, commands, and validation checkpoints for generating and verifying contracts
Remove the 'How It Works' and 'When to Use' sections which explain concepts Claude already knows, replacing them with concrete implementation patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what contract testing is, how Pact works conceptually). The 'How It Works' and 'When to Use' sections repeat information from the description without adding actionable value. | 1 / 3 |
Actionability | No executable code, commands, or concrete examples are provided. The 'Examples' section describes what the skill 'will do' abstractly rather than showing actual Pact test code, OpenAPI validation commands, or specific implementation patterns. | 1 / 3 |
Workflow Clarity | The numbered steps are vague descriptions ('Analyze the API', 'Create provider verification tests') without concrete commands, validation checkpoints, or error handling. No actual workflow for generating or running contract tests is provided. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, but it's a monolithic document with no references to external files for detailed examples, API references, or advanced usage patterns that would benefit from separation. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.