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.
94
93%
Does it follow best practices?
Impact
93%
1.10xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 follows best practices. It uses third person voice, lists specific capabilities and tools, includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche in contract testing 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 tool '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', 'breaking changes', 'OpenAPI specifications', 'Pact', 'schema validation'. Good coverage of terms developers naturally use when discussing contract testing. | 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 that provides actionable, executable code examples for API contract testing with Pact and OpenAPI. The content is concise and well-organized with appropriate progressive disclosure to reference files. The main weakness is the lack of an explicit end-to-end workflow showing the sequence of consumer test → publish → provider verify → deploy, which would help Claude understand the complete testing lifecycle.
Suggestions
Add a numbered workflow section showing the complete contract testing lifecycle: 1) Write consumer test, 2) Generate pact file, 3) Publish to broker, 4) Provider verifies, 5) Can-I-Deploy check, 6) Deploy
Include explicit validation checkpoint after provider verification showing how to check results before proceeding with deployment
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using a table for definitions rather than verbose explanations. Code examples are complete without unnecessary commentary, and every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable TypeScript and JavaScript code examples that are copy-paste ready. The Pact consumer test, provider verification, and OpenAPI validation examples are complete and immediately usable. | 3 / 3 |
Workflow Clarity | While the consumer-provider relationship is clear and examples show both sides, there's no explicit workflow sequence showing how to run consumer tests first, publish contracts, then verify on provider side. Missing validation checkpoints for the CI/CD integration process. | 2 / 3 |
Progressive Disclosure | Excellent structure with core concepts and primary examples in the main file, 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
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.
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- 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.