validating-api-contracts
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill validating-api-contractsThis 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content describes what contract testing is rather than instructing Claude how to do it. It lacks any executable code, specific commands, or concrete examples that would make it actionable. The content reads like documentation for a human user rather than instructions for Claude.
Suggestions
Replace the abstract 'Examples' section with actual executable Pact test code showing consumer contract generation and provider verification
Add specific commands for running contract tests (e.g., `pact-verifier --provider-base-url=...`) and OpenAPI validation tools
Remove the 'How It Works', 'When to Use', and 'Best Practices' sections - Claude already knows these concepts and they waste tokens
Add a concrete workflow with validation steps: generate contract → run consumer tests → publish pact → verify provider → check for breaking changes
| 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 | Steps are vague ('Analyze the API', 'Create provider verification tests') with no concrete sequence, validation checkpoints, or error handling. There's no guidance on what files to create, what commands to run, or how to verify success. | 1 / 3 |
Progressive Disclosure | The content has some structure with clear section headers, but everything is inline with no references to detailed documentation. The content that exists could be much more concise, and detailed examples/reference material should be split out. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities (Pact testing, OpenAPI validation, breaking change detection), includes comprehensive trigger terms that users would naturally use, and clearly delineates both what the skill does and when to use it. The technical domain is narrow enough to avoid conflicts 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'. | 3 / 3 |
Completeness | Clearly answers both what (validates API contracts using Pact and OpenAPI) 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-test', 'ct', 'Pact', 'OpenAPI validation', 'consumer-driven contract testing', 'generate contract tests', 'validate API responses', 'check backward compatibility'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on contract testing and OpenAPI validation with distinct triggers like 'Pact', 'contract-test', 'ct', and 'consumer-driven contract testing' that are unlikely to conflict with general API or testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
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.