CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/contract-compatibility-gate

Builds a unified deployment-readiness gate that aggregates verdicts from any combination of Pact `can-i-deploy`, oasdiff (OpenAPI), graphql-inspector (GraphQL), and `buf breaking` (Protobuf), applies severity-aware pass/fail thresholds, and emits a single go / no-go decision with per-finding rationale. Use when authoring a CI step that gates a deployment on cross-protocol contract compatibility.

75

Quality

94%

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

85%

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

A well-structured body with concrete artifacts (record shape, decision function, command examples), a clear sequenced workflow, and clean one-level progressive disclosure to a verified reference. The main weakness is mild verbosity in the Overview and Worked example sections.

Suggestions

Tighten the Overview prose that explains each tool's exit codes and 'concept of breaking' — the table already conveys this; trim the surrounding explanation.

Shorten the narrated Worked example by leaning on the JSON record list and summary block already shown; the step-by-step prose largely repeats earlier sections.

Consider moving the per-field record-shape rationale table into the reference file if token budget is a concern, keeping only the JSON shape inline.

DimensionReasoningScore

Conciseness

Mostly efficient — the severity-normalization table, unified record shape, and decision function are dense and earned — but the Overview intro and the narrated Worked example re-explain tool semantics and re-walk the flow in prose that could be tightened.

2 / 3

Actionability

Provides an executable `gate_decision` Python function, a concrete JSON record shape, concrete tool commands in the worked example (e.g. `oasdiff breaking --format json`, `buf breaking --error-format json`), and defers the full gate script/CI wiring to a real reference file.

3 / 3

Workflow Clarity

A clear five-step sequence (identify sources -> normalize -> classify severity -> apply gate -> emit and exit) with the gate_decision rule serving as the explicit pass/fail checkpoint and a non-zero exit on no-go.

3 / 3

Progressive Disclosure

SKILL.md is an overview that repeatedly and clearly signals a single one-level-deep reference, references/gate-implementation-and-ci.md (verified to exist), keeping the full gate script, CI wiring, and artifact format out of the main body.

3 / 3

Total

11

/

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 names concrete capabilities, named tools, and an explicit trigger clause covering both what the skill does and when to use it. It is distinctive and unlikely to misfire.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (aggregates verdicts from named tools, applies severity-aware thresholds, emits a single go/no-go decision with per-finding rationale) rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (aggregates, applies thresholds, emits decision) and 'when' via the 'Use when authoring a CI step that gates a deployment on cross-protocol contract compatibility' clause.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered — 'CI step', 'deployment', 'gate', 'contract compatibility' alongside the named tools a user would name when they need this skill.

3 / 3

Distinctiveness Conflict Risk

A clearly defined niche — cross-protocol contract compatibility gating across four specific named tools — that is unlikely to trigger for or conflict with unrelated skills.

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