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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-contract-testing/skills/api-contract-testing/SKILL.md

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly executable skill body that uses progressive disclosure effectively to keep the overview short while offloading per-language detail to real reference files. Its main weakness is workflow clarity: the consumer-to-provider verification sequence and CI publishing step are implied rather than sequenced with explicit validation checkpoints.

Suggestions

Add a short numbered workflow (1. write/verify consumer pact, 2. publish to broker, 3. verify provider against broker, 4. check verification result in CI) so the end-to-end sequence is explicit.

Include an explicit validation checkpoint for the CI publish/verify step (e.g. 'Only deploy when provider verification passes') rather than relying on the Do/Don't list.

Trim the Key Concepts table to only terms that are not common knowledge (e.g. Pact, Broker) to reduce tokens explaining concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — concept table, executable snippets, and terse Do/Don't and Tools lists with minimal over-explanation — though the Key Concepts table restates definitions Claude already knows, a small amount of padding.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript/JavaScript for consumer tests, provider verification, and OpenAPI validation, plus pointers to runnable Python and Java reference implementations covering the common cases.	5 / 5
Workflow Clarity	The contract-testing flow is implicit (write consumer pact -> verify on provider) rather than sequenced as numbered steps, and there is no explicit validation checkpoint for the batch/CI publish-to-broker operation, capping clarity at 3.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with clearly signaled, one-level-deep references to three real bundle files (python-json-schema.md, java-rest-assured.md, pact-broker-cicd.md), each linked inline under an 'Additional Implementations' section; content is appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both capability and trigger conditions in third person with concrete, recognizable trigger phrases. Minor gains are possible by adding a few more natural synonyms and tightening the action list for fuller coverage.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('consumer-driven contracts, schema validation' and the tool 'Pact') with specific verbs like 'Verifies', but does not enumerate a comprehensive set of actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both what it does ('Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact') and when to use it ('Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications').	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('testing microservices communication', 'preventing breaking changes', 'validating OpenAPI specifications') with good coverage, though a few common synonyms (e.g. 'Swagger', 'consumer-driven') are only weakly present.	4 / 5
Distinctiveness Conflict Risk	The 'consumer-driven contracts' and Pact framing carves a clear niche with mostly distinct triggers, though 'schema validation' and 'OpenAPI' create minor overlap with generic schema-validation or API-testing skills.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Path: plugins/api-contract-testing/skills/api-contract-testing/SKILL.md
Commit: 84802a4

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.