api-contract-testing
Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill api-contract-testingOverall
score
92%
Does it follow best practices?
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 capabilities (contract verification, schema validation), names concrete tools (Pact), includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche in the API contract testing space that won't overlap with general API or testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Verifies API contracts', 'consumer-driven contracts', 'schema validation', and mentions specific tools like 'Pact'. Also references concrete artifacts like 'OpenAPI specifications'. | 3 / 3 |
Completeness | Clearly answers both what ('Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact') and when ('Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'API contracts', 'microservices', 'Pact', 'breaking changes', 'OpenAPI specifications', 'schema validation'. These cover both technical terms and problem-oriented language users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on contract testing between services with distinct triggers like 'Pact', 'consumer-driven contracts', 'API contracts', and 'OpenAPI specifications'. Unlikely to conflict with general API testing or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability through complete, executable code examples and good progressive disclosure via linked references. The main weakness is the lack of an explicit end-to-end workflow showing how consumer tests, broker publishing, and provider verification connect in a CI/CD pipeline, which would help Claude understand the full contract testing lifecycle.
Suggestions
Add a brief workflow section showing the sequence: 1) Consumer writes/runs tests → 2) Publish contracts to broker → 3) Provider verifies → 4) Can-I-Deploy check before release
Include a validation checkpoint showing how to verify contracts were published successfully before provider verification
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using a table for definitions rather than prose explanations. No unnecessary explanations of concepts Claude would already know - jumps straight to executable examples. | 3 / 3 |
Actionability | Provides fully executable TypeScript and JavaScript code examples that are copy-paste ready. Includes complete test setup, matchers, state handlers, and middleware configuration with realistic scenarios. | 3 / 3 |
Workflow Clarity | While the consumer test and provider verification are shown separately, there's no explicit workflow connecting them (e.g., 'run consumer tests first, publish to broker, then verify provider'). Missing validation checkpoints for the contract testing lifecycle. | 2 / 3 |
Progressive Disclosure | Excellent structure with core concepts and primary examples inline, while appropriately linking to separate reference files for Python, Java, and CI/CD implementations. References are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 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.