CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contract-testing

Use when setting up integration testing for a frontend-backend API boundary, evaluating whether two services are safe to deploy independently, or replacing slow end-to-end tests with contract tests.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/contract-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 overview body with exemplary progressive disclosure: lean sections, a clear signaled pointer to a complete reference file, and no nested references. The weaknesses are the absence of any inline executable example or command and the lack of validation checkpoints (publish confirmation, can-i-deploy gate) in the workflow the body sketches.

Suggestions

Inline one minimal executable anchor in the body — e.g., the two-line Pact test skeleton or the publish command — so the skill is immediately actionable before opening the reference.

Mention the deploy-safety validation gate in the Fix section (e.g., 'gate deploys on the broker's can-i-deploy check') so the workflow includes an explicit checkpoint rather than ending at provider verification.

Trim the three-sentence motivation intro to one sentence and drop the duplicated rule-page URL (already in frontmatter) to reach full token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and checklist-style with one-line directives per section; every token mostly earns its place. Minor trimmable parts remain: the three-sentence motivation intro restates knowledge Claude already has, and the trailing 'Rule page' URL duplicates the frontmatter url.

4 / 5

Actionability

Directives are concrete at the tool level — 'Add Pact consumer tests for the frontend API client, publish the contracts to a broker, and add provider verification to the backend CI pipeline' plus specific review criteria ('any-type matchers', 'missing status code assertions') — but the body itself contains no executable code or commands; the executable detail lives one reference away in references/rule.md.

3 / 5

Workflow Clarity

A coherent sequence is present (Quick Reference and Fix sections: consumer tests → publish to broker → provider verification in CI), but the body has no validation checkpoints such as confirming the contract was published or gating deploys on verification (e.g., a can-i-deploy check), which the reference file covers but the overview does not signal.

3 / 5

Progressive Disclosure

The body is a concise, well-organized overview that clearly signals exactly one one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists with the complete content and nests no further references. This is the ideal overview-plus-reference split.

5 / 5

Total

15

/

20

Passed

Description

61%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 well-focused, trigger-heavy description with concrete scenarios and natural phrasing, but it omits any third-person capability statement of what the skill actually does, leaving the 'what' implied. Adding tool keywords like Pact and consumer-driven would strengthen both trigger coverage and completeness.

Suggestions

Prepend a capability statement in third person, e.g., 'Implements consumer-driven contract testing with Pact: writes consumer tests, publishes contracts to a broker, and wires provider verification into CI.'

Add the tool names users actually say — 'Pact', 'Pact Broker', 'consumer-driven contract testing' — as trigger terms so users asking about those tools find the skill.

Sharpen the first trigger ('setting up integration testing') toward contract testing specifically, e.g., 'setting up API contract testing', to reduce overlap with a generic integration-testing skill.

DimensionReasoningScore

Specificity

The description names a concrete domain ('frontend-backend API boundary', 'contract tests') with three specific scenarios, but it never states the skill's own capabilities (e.g., writing Pact consumer tests, publishing to a broker, adding provider verification), so coverage of concrete actions is not comprehensive.

3 / 5

Completeness

The 'when' is explicit and richly detailed across three trigger scenarios, but the description is entirely 'Use when...' clauses with no 'what' — the skill's capability statement is only implied by the trigger conditions. It is stronger than anchor 2's vague when-only example, but does not reach 4, which requires both a clear what and when.

3 / 5

Trigger Term Quality

Natural phrases like 'setting up integration testing', 'slow end-to-end tests', 'safe to deploy independently', and 'contract tests' match what users would actually say. It falls short of 5 because key synonyms a user might use — 'Pact', 'consumer-driven', 'API contract' — are absent.

4 / 5

Distinctiveness Conflict Risk

Niche triggers like 'frontend-backend API boundary' and 'contract tests' give it a clear domain with minimal conflict risk. Minor overlap remains with a generic integration-testing or end-to-end-testing skill via the opening phrase 'setting up integration testing'.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/contract-testing/SKILL.md

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.