fixture-generator
Fixture Generator - Auto-activating skill for Test Automation. Triggers on: fixture generator, fixture generator Part of the Test Automation skill category.
36
Quality
7%
Does it follow best practices?
Impact
88%
0.95xAverage 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/fixture-generator/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 just restating the skill name without explaining what it actually does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term ('fixture generator' listed twice) suggests this may be auto-generated boilerplate that was never properly filled in.
Suggestions
Add specific actions describing what the skill does, e.g., 'Generates test fixtures including mock data, database seeds, and API response stubs for automated testing'
Include a 'Use when...' clause with natural trigger terms like 'test data', 'mock objects', 'sample data', 'test fixtures', 'stub data', or 'seed data'
Specify the types of fixtures supported (unit test, integration test, database, API) to distinguish from other testing skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names 'Fixture Generator' without describing any concrete actions. It doesn't explain what fixtures are generated, how they're generated, or what the output looks like. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'fixture generator' repeated twice, which is redundant and doesn't include natural variations users might say like 'test data', 'mock data', 'test fixtures', 'generate fixtures', or 'sample data'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Test Automation' and 'fixture generator' provide some domain specificity, the lack of detail about what kind of fixtures (database, API, unit test, etc.) could cause overlap with other testing-related skills. | 2 / 3 |
Total | 5 / 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 is a hollow template with no actionable content. It describes what a fixture generator skill would do without providing any actual guidance, code examples, or workflows for generating test fixtures. The content fails to teach Claude anything it doesn't already know.
Suggestions
Add concrete, executable code examples showing how to generate fixtures in specific frameworks (e.g., pytest fixtures, Jest factories)
Include a clear workflow: identify test data needs → choose fixture pattern → implement fixture → validate fixture works
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific fixture patterns and anti-patterns
Add example inputs and outputs showing what a fixture request looks like and what the generated fixture code should be
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire skill describes what it does abstractly without showing how to actually generate fixtures. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for fixture generation. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there are no references to detailed materials, examples, or external files. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
f17dd51
- 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.