test-data-builder
Test Data Builder - Auto-activating skill for Test Automation. Triggers on: test data builder, test data builder Part of the Test Automation skill category.
33
0%
Does it follow best practices?
Impact
96%
1.00xAverage 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/test-data-builder/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 with no substantive content. It lacks concrete actions, meaningful trigger terms, explicit usage guidance, and any distinguishing detail. It would be nearly impossible for Claude to correctly select this skill from a pool of similar test-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates test data objects using the builder pattern, creates mock/fake data for unit and integration tests, produces factory fixtures for database seeding.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating test data, building test fixtures, generating mock objects, factory patterns, or seeding test databases.'
Remove the duplicate trigger term and expand with natural variations users would actually say, such as 'test fixtures', 'mock data', 'fake data', 'sample data', 'test factory', 'seed data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names the concept 'Test Data Builder' and mentions 'Test Automation' as a category, but never describes what the skill actually does (e.g., generates mock data, creates fixtures, builds factory objects). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no meaningful 'Use when...' clause—only a redundant trigger term and a vague category label. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'test data builder' repeated twice. There are no natural variations a user might say such as 'test fixtures', 'mock data', 'factory pattern', 'sample data', 'test objects', or 'seed data'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to distinguish this skill from other test-related skills. 'Test Automation' is a broad category, and without specific actions or clear triggers, it could easily conflict with skills for test generation, test running, or other test data utilities. | 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 a hollow placeholder that contains no actual instructional content. It describes what it would do in abstract terms but provides zero actionable guidance on test data builders — no code, no patterns, no examples, no workflows. It reads like auto-generated boilerplate rather than a functional skill.
Suggestions
Add concrete, executable code examples showing the Test Data Builder pattern (e.g., a Builder class in Python/Java/TypeScript with fluent API for constructing test objects).
Include a clear workflow: 1) identify the domain object, 2) create the builder with sensible defaults, 3) override specific fields in tests, 4) validate the built object — with actual code for each step.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill itself rather than teaching the pattern — these waste tokens on information Claude doesn't need.
Add at least one complete before/after example showing how test data builders improve test readability compared to raw object construction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding. | 1 / 3 |
Actionability | There is zero concrete, executable guidance — no code examples, no specific commands, no patterns, no actual test data builder implementation. The entire content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic description with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization beyond generic headings. | 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.