fixture-generator
Fixture Generator - Auto-activating skill for Test Automation. Triggers on: fixture generator, fixture generator Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill fixture-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped and essentially non-functional for skill selection. It provides no information about what the skill actually does, repeats the same trigger term twice, and lacks any explicit usage guidance. Claude would have no basis to select this skill appropriately from a pool of available skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates test fixtures, mock objects, and sample data for unit and integration tests'
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs test data, mock objects, fixture files, or sample inputs for testing'
Expand trigger terms to include natural variations: 'test fixtures', 'mock data', 'test data', 'sample data', 'stub generation', 'factory data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Fixture Generator') and category ('Test Automation') without describing any concrete actions. There's no indication of what the skill actually does - no verbs describing capabilities like 'generates', 'creates', or 'processes'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit 'Use when...' clause). The 'Triggers on' line is not a proper usage guidance - it just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'fixture generator' repeated twice, which is redundant and overly narrow. Missing natural variations users might say like 'test fixtures', 'mock data', 'test data generation', 'sample data', or 'stub generation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Fixture Generator' is somewhat specific to testing contexts, the lack of detail about what kind of fixtures (database, API, unit test) or what format/language could cause overlap with other test-related skills. The category mention helps slightly. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what a fixture generator skill would do in abstract marketing language but provides zero actionable guidance, no code examples, no specific patterns, and no actual instructions for generating test fixtures.
Suggestions
Add concrete, executable code examples showing how to generate fixtures in at least one framework (e.g., pytest fixtures, Jest factories)
Include specific patterns for common fixture types: database records, mock objects, API response stubs, with copy-paste ready code
Define a clear workflow for fixture generation: identify test needs → choose fixture pattern → implement → validate fixture behavior
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire skill describes what it does in abstract terms without showing how to actually generate fixtures or providing any specific implementation details. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill merely lists vague capabilities without explaining how to accomplish any fixture generation task. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no examples, and no navigation to supporting documentation. It mentions related skills but provides no actual links or content organization. | 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.