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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill test-data-builderOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks concrete actions, meaningful trigger terms (with a duplicate entry), and any guidance on when to use the skill. The only distinguishing element is the skill name itself.
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 explicit triggers, e.g., 'Use when the user needs mock data, test fixtures, fake records, or sample objects for testing purposes'
Expand trigger terms to include natural variations users would say: 'mock data', 'test fixtures', 'fake data', 'sample records', 'factory patterns', 'test objects'
| 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 explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 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 might say like 'mock data', 'test fixtures', 'fake data', 'sample data', or 'test objects'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Test Data Builder' is somewhat specific to a testing context, 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. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what a test data builder skill should do but provides zero concrete guidance, code examples, or patterns. Claude would gain nothing from this skill that it doesn't already know.
Suggestions
Add concrete, executable code examples showing the Builder pattern for test data (e.g., a UserBuilder class with fluent methods)
Include specific examples for common test data scenarios: valid data, edge cases, invalid data for negative testing
Provide a clear workflow: 1) Identify entity to build, 2) Create builder with sensible defaults, 3) Add methods for common variations, 4) Show usage in actual tests
Reference or link to framework-specific implementations (Jest factories, pytest fixtures, etc.) rather than just listing tags
| 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 | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('Generates production-ready code') but never shows how to actually build test data or provides any examples. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes when the skill activates and what it claims to do, without any actual sequence of actions for building test data. | 1 / 3 |
Progressive Disclosure | No structure for discovery or navigation. The content is a flat list of generic sections with no references to detailed materials, examples, or related documentation that would help Claude actually perform test data builder tasks. | 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.