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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill contract-test-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially only providing the skill name repeated as trigger terms. It lacks any explanation of what contract testing involves, what specific actions the skill performs, or meaningful guidance for when Claude should select it over other testing-related skills.
Suggestions
Add specific 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 proper 'Use when...' clause with natural trigger terms like 'API contract', 'consumer-driven testing', 'pact tests', 'service integration validation', 'provider verification'
Remove the duplicate 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 specific capabilities listed like 'generates contract tests', 'validates API schemas', or 'creates mock services'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a circular reference to the skill name. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('contract test creator, contract test creator') and only repeat the skill name. Missing natural variations users would say like 'API contract', 'consumer-driven tests', 'pact tests', 'service contracts', or 'integration testing'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'contract test' is somewhat specific to a testing domain, which provides some distinctiveness. However, without concrete actions or clear triggers, it could overlap with general testing skills or API testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no substantive content about contract testing. It lacks any concrete guidance on contract test frameworks (Pact, Spring Cloud Contract), consumer/provider patterns, or executable examples. The content describes meta-information about the skill rather than teaching Claude how to actually create contract tests.
Suggestions
Add concrete code examples using a contract testing framework like Pact, showing both consumer and provider test setup
Define a clear workflow: 1) Define consumer expectations, 2) Generate contract, 3) Verify provider against contract, 4) Publish/share contracts
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific contract testing patterns and anti-patterns
Include example contract definitions (JSON/YAML) and the corresponding test code that validates them
| 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 entire skill describes what it does rather than instructing how to create contract tests. There are no examples of actual contract test patterns, frameworks (like Pact), or executable code. | 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 lists vague 'capabilities' without any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to examples, API documentation, or advanced topics are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.