CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pact-contract-testing

Authors and verifies Pact consumer-driven contract tests across the full Pact lifecycle - consumer tests producing pact files, publishing to the Pact Broker, provider verification, and `can-i-deploy` deployment gates. Use when introducing a new HTTP/JSON API contract between two services, diagnosing breaking changes, or wiring contract verification into CI.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A well-structured skill body that moves cleanly through the Pact lifecycle with executable code, concrete commands, and explicit validation gates, while pushing detailed CI pipelines to a single clearly-linked reference file. It assumes Claude's competence and wastes few tokens.

DimensionReasoningScore

Conciseness

The body is lean — the five-step lifecycle, code blocks, and flag tables each earn their place and avoid explaining basic concepts Claude already knows; guidance like 'prefer openapi-contract-diff' is terse and decisive.

3 / 3

Actionability

Provides fully executable examples at every stage — PactV3 consumer test, pact-broker publish/verify/can-i-deploy/record-deployment commands, and Verifier with stateHandlers — copy-paste ready with real flags.

3 / 3

Workflow Clarity

The lifecycle is explicitly sequenced (consumer test → pact file → publish → verify → can-i-deploy) with the can-i-deploy exit codes as the validation gate and a clear feedback note that record-deployment prevents spurious 'no' verdicts.

3 / 3

Progressive Disclosure

SKILL.md serves as an overview and offloads full CI pipeline YAML to a single, clearly signaled one-level-deep reference (references/ci-pipelines.md), which exists in the bundle.

3 / 3

Total

12

/

12

Passed

Description

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.

A strong, third-person description that concretely enumerates the Pact lifecycle actions and pairs them with explicit, natural trigger conditions. It satisfies the what/when requirement and is well differentiated.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the lifecycle — 'consumer tests producing pact files, publishing to the Pact Broker, provider verification, and `can-i-deploy` deployment gates' — rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what ('Authors and verifies Pact consumer-driven contract tests across the full Pact lifecycle') and when (the 'Use when...' clause), matching the top anchor.

3 / 3

Trigger Term Quality

Natural phrasing a user would say ('introducing a new HTTP/JSON API contract between two services, diagnosing breaking changes, or wiring contract verification into CI') with good coverage of real-world triggers.

3 / 3

Distinctiveness Conflict Risk

The Pact consumer-driven contract testing niche is distinct and unlikely to trigger for unrelated skills; it even names the alternative (openapi-contract-diff) elsewhere to disambiguate.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents