generating-test-data
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
89
53%
Does it follow best practices?
Impact
96%
1.00xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/test-data-generator/skills/test-data-generator/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly communicates what the skill does, when to use it, and includes natural trigger phrases. It lists specific data types (users, products, orders, custom schemas) and concrete use cases (populating databases, creating fixtures, simulating behavior). The explicit trigger phrases section is particularly well done, covering multiple natural variations a user might say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generate users, products, orders, custom schemas, populate databases, simulate user behavior, create fixtures for automated tests. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates realistic test data including users, products, orders, custom schemas) and 'when' (explicit trigger phrases and use cases like populating databases, simulating user behavior, creating fixtures). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger phrases users would actually say: 'generate test data', 'create fake users', 'populate database', 'generate product data', 'create test orders', 'generate data based on schema'. These cover a wide range of natural user language. | 3 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused specifically on test data generation with distinct triggers like 'fake users', 'test orders', 'populate database'. Unlikely to conflict with other skills due to the specific domain of test data generation. | 3 / 3 |
Total | 12 / 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 content is almost entirely descriptive and abstract, lacking any concrete plugin invocation syntax, executable code, example outputs, or specific parameters. It reads more like a marketing description of a feature than an actionable skill file. The verbosity is high while the actionable information density is near zero.
Suggestions
Add concrete plugin invocation syntax showing exactly how to call the test-data-generator plugin with specific parameters (e.g., data type, count, locale, seed).
Include at least one complete example with actual input parameters and expected output (e.g., a sample JSON snippet of generated user data).
Remove the 'How It Works', 'When to Use This Skill', and 'Integration' sections entirely — these describe concepts Claude already knows and add no actionable value.
Add a quick-reference section showing the available data types, required vs optional parameters, and any schema definition format the plugin expects.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly verbose, explaining concepts Claude already knows (what test data is, when to use it, how the process works at a high level). Sections like 'How It Works', 'When to Use This Skill', and 'Integration' add little actionable value and mostly restate the description. Nearly every sentence could be cut or condensed. | 1 / 3 |
Actionability | There is no concrete, executable code, no specific commands, no actual plugin invocation syntax, and no example output. The examples describe what the skill 'will do' in abstract terms rather than showing how to actually invoke the plugin or what the generated data looks like. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists three vague steps (identify, generate, present) with no concrete commands, no validation checkpoints, and no error handling. The examples similarly describe abstract steps ('invoke the plugin') without showing actual invocation syntax or verification of output. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headings, which provides some structure. However, there are no references to external files, no bundle files to reference, and the content is a monolithic set of sections that could be more concise rather than needing to be split. The organization is adequate but the content within sections is padded. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.