contract-test-creator
Contract Test Creator - Auto-activating skill for Test Automation. Triggers on: contract test creator, contract test creator Part of the Test Automation skill category.
38
Quality
7%
Does it follow best practices?
Impact
95%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/contract-test-creator/SKILL.mdQuality
Discovery
7%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 description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and lack of concrete actions make this description nearly useless for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates consumer-driven contract tests, validates API schemas against contracts, creates Pact or Spring Cloud Contract specifications'
Include a 'Use when...' clause with natural trigger terms like 'API contract testing', 'consumer-driven contracts', 'Pact tests', 'service integration validation', 'contract verification'
Remove the redundant trigger term and expand with variations users would naturally say when needing contract testing help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Contract Test Creator') without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what creating contract tests actually involves. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'contract test creator' repeated twice, which is redundant and overly narrow. Missing natural variations users might say like 'API contract', 'consumer-driven contracts', 'pact tests', 'service contracts', or 'integration testing'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'contract test' is somewhat specific to a testing niche, the lack of detail about what distinguishes this from general test creation or other testing skills creates potential overlap. The category 'Test Automation' suggests other testing skills exist that could conflict. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual instructional content. It describes what a contract test creator skill would do but provides zero actionable guidance on how to create contract tests - no code examples, no framework recommendations (Pact, Spring Cloud Contract, etc.), no workflow for defining consumer/provider contracts, and no validation steps.
Suggestions
Add concrete code examples showing how to create contract tests using a specific framework like Pact or Spring Cloud Contract
Define a clear workflow: 1) Define consumer expectations, 2) Generate contract, 3) Verify provider against contract, 4) Publish to broker
Remove meta-descriptions ('This skill provides automated assistance...') and replace with actual executable guidance
Include specific examples of contract definitions (e.g., Pact DSL syntax) and verification commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually create contract tests - no examples, no frameworks, no executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating contract tests, no validation checkpoints, and no sequence of operations. The content only describes triggers and capabilities at a meta level. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there are no references to detailed materials, examples, or external files. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
f17dd51
- 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.