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.
36
Quality
3%
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
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 serving as a placeholder rather than a functional skill description. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and boilerplate structure suggest this was auto-generated without customization.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates mock objects, creates test fixtures, builds sample datasets for unit and integration tests'
Add a 'Use when...' clause with natural trigger terms like 'mock data', 'test fixtures', 'fake data', 'sample records', 'factory pattern', 'test objects'
Remove the duplicate trigger term and expand with variations users would naturally say when needing test data generation
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Test Data Builder') without describing any concrete actions. There are no specific capabilities listed like 'generates mock data', 'creates fixtures', or 'builds test objects'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Only states it's 'auto-activating' without explaining the activation conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('test data builder, test data builder' - duplicated) and only cover the exact skill name. Missing natural variations users would say like 'mock data', 'test fixtures', 'fake data', 'sample data', 'factory'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Test Data Builder' is somewhat specific to a domain, the lack of concrete actions means it could overlap with other testing-related skills. The category mention ('Test Automation') provides some context but doesn't clearly distinguish it from other test automation skills. | 2 / 3 |
Total | 5 / 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 substantive content. It describes what a test data builder skill would do but provides absolutely no actionable guidance, code examples, patterns, or concrete instructions. The entire content is meta-description rather than actual skill content.
Suggestions
Add concrete, executable code examples showing how to implement the Builder pattern for test data (e.g., a UserBuilder class with fluent methods)
Include specific patterns like factory functions, faker integration, or fixture builders with copy-paste ready code
Provide at least one complete example showing input scenario and expected test data output
Remove all meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague filler that Claude doesn't need to be told. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions on how to build test data. The skill describes what it does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints. The content only describes when the skill activates, not how to perform any task. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to disclose. There are no references to detailed materials, examples, or supporting documentation. | 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
60433a6
- 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.