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".
68
53%
Does it follow best practices?
Impact
90%
0.94xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/contract-test-validator/skills/contract-test-validator/SKILL.mdQuality
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 strong skill description that clearly articulates specific capabilities (contract testing with Pact, OpenAPI validation, breaking change detection), provides explicit trigger guidance with both natural language scenarios and shorthand terms, and occupies a distinct niche unlikely to conflict with other skills. The description uses proper third-person voice throughout and balances detail with conciseness effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: validates API contracts, consumer-driven testing, OpenAPI validation, leverages Pact, validates against OpenAPI specifications, identifies breaking changes, generates contract tests, validates API responses, and checks backward compatibility. | 3 / 3 |
Completeness | Clearly answers both 'what' (validates API contracts using consumer-driven testing and OpenAPI validation, identifies breaking changes) and 'when' with an explicit 'Use this skill when...' clause listing specific trigger scenarios and terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'contract tests', 'validate API responses', 'backward compatibility', 'contract-test', 'ct', 'Pact', 'OpenAPI validation', and 'consumer-driven contract testing'. These cover both shorthand and full-form terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around API contract testing, Pact, and OpenAPI validation. The specific trigger terms like 'contract-test', 'ct', 'Pact', and 'consumer-driven contract testing' are unlikely to conflict with general API testing or other skills. | 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 is essentially a marketing description of what contract testing is, rather than an actionable guide for Claude. It contains no executable code, no concrete examples of Pact contracts or OpenAPI validation, and no specific commands or library usage. The entire body could be replaced with 20 lines of actual Pact test code and OpenAPI validation snippets that would be far more useful.
Suggestions
Add complete, executable Pact consumer test code examples (e.g., using pact-python or pact-js) with actual interaction definitions, matchers, and provider verification setup.
Include concrete OpenAPI validation code using a specific library (e.g., openapi-spec-validator, schemathesis) with example commands and expected output.
Remove the 'How It Works', 'When to Use', 'Best Practices', and 'Integration' sections entirely — they explain concepts Claude already knows and waste tokens.
Add a workflow with explicit validation checkpoints, e.g., 'Run pact verify → check output for failures → fix provider → re-verify' with actual CLI commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains things Claude already knows (what contract testing is, what Pact does, when to use it). The 'How It Works', 'When to Use', 'Best Practices', and 'Integration' sections are all filler that add no actionable value. The description already covers activation triggers, making the 'When to Use' section redundant. | 1 / 3 |
Actionability | There is zero executable code, no concrete commands, no actual Pact test examples, no OpenAPI validation snippets, and no specific library imports or configurations. The 'examples' merely describe what the skill will do in abstract terms rather than showing how to do it. | 1 / 3 |
Workflow Clarity | The multi-step processes described (generate contracts, validate, check compatibility) are vague and lack any concrete sequencing, validation checkpoints, or error recovery steps. Steps like 'Analyze the API and generate Pact consumer contracts' provide no actionable detail. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with clear section headers, but there are no references to external files, no bundle files to support deeper content, and the inline content is shallow rather than appropriately split. The sections are well-labeled but contain little substance. | 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.
- Commit
13d35b8
- 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.