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.
33
0%
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
0%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 essentially a placeholder that repeats the skill name without providing any substantive information about capabilities, concrete actions, or usage triggers. It would be nearly impossible for Claude to reliably select this skill from a pool of similar testing-related skills. The duplicate trigger term and lack of any 'Use when...' clause make it one of the weakest possible descriptions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates consumer-driven contract tests, creates provider verification stubs, validates API schemas against contracts.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about contract testing, consumer-driven contracts, Pact tests, API contract validation, provider stubs, or schema compatibility checks.'
Remove the duplicate trigger term and replace with varied, natural keywords users would actually say, such as 'Pact', 'API contract', 'consumer test', 'provider verification', 'contract-first testing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('contract test creator', 'Test Automation') but provides no concrete actions. There is no indication of what specific tasks this skill performs—no verbs like 'generates', 'validates', 'creates stubs', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when should Claude use it' clause. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'contract test creator' repeated twice. There are no natural user keywords like 'consumer-driven contract', 'Pact', 'API contract', 'provider test', 'schema validation', or other terms a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic within the testing domain. 'Test Automation' could overlap with many other testing skills, and 'contract test creator' without further specificity doesn't clearly carve out a niche from other test generation or API testing skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder template with no actual content. It contains no executable code, no concrete guidance on contract testing, no mention of specific tools (Pact, Spring Cloud Contract, etc.), and no workflows. Every section is abstract meta-description that tells Claude what the skill supposedly does without actually teaching it anything.
Suggestions
Add concrete, executable code examples for creating contract tests using a specific framework (e.g., Pact for consumer-driven contract tests) with both provider and consumer side examples.
Define a clear multi-step workflow: 1) Define consumer expectations, 2) Generate contract/pact file, 3) Verify provider against contract, 4) Validate results—with explicit validation checkpoints.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace with actual technical content covering contract test patterns, tool configuration, and common pitfalls.
Add references to supplementary files for advanced topics (e.g., PACT_BROKER.md for CI/CD integration, EXAMPLES.md for different language implementations) to enable progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('contract test creator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific examples of contract tests, no mention of tools like Pact or Spring Cloud Contract. The 'Example Triggers' are just rephrased ways to ask for help, not actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured sections with real content, and no navigation to deeper resources. | 1 / 3 |
Total | 4 / 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
3076d78
- 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.