fixture-generator
Fixture Generator - Auto-activating skill for Test Automation. Triggers on: fixture generator, fixture generator Part of the Test Automation skill category.
32
0%
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
0%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 essentially a placeholder with no substantive content. It lacks concrete actions, meaningful trigger terms, explicit usage guidance, and any distinguishing details. The repeated trigger term 'fixture generator' and generic category label 'Test Automation' provide almost no useful information for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates test fixture files with mock data for unit and integration tests, creates factory functions, and scaffolds seed data for test databases.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create test fixtures, mock data, factory functions, test data, seed data, or sample objects for testing frameworks like pytest, Jest, or RSpec.'
Include distinguishing details such as supported languages, frameworks, or fixture formats to differentiate from other testing-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Test Automation') and a concept ('Fixture Generator') but does not describe any concrete actions. There are no specific capabilities listed—no verbs like 'generates', 'creates', or 'configures' that explain what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions) and 'when should Claude use it' (no explicit 'Use when...' clause or equivalent guidance). The 'Triggers on' line is just a repeated label, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'fixture generator' repeated twice. There are no natural keyword variations a user might say, such as 'test fixtures', 'mock data', 'test data generation', 'factory', 'seed data', or similar terms. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Test Automation' is a broad category, and without specifying what kind of fixtures, for what frameworks, or in what context, it could easily conflict with other testing-related skills. | 1 / 3 |
Total | 4 / 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 with no substantive content. It contains only meta-descriptions and trigger phrases but provides zero actual guidance on generating test fixtures. It fails on every dimension because it teaches nothing—there are no code examples, no framework-specific instructions, no workflows, and no references to detailed materials.
Suggestions
Add concrete, executable code examples for fixture generation in at least one framework (e.g., pytest fixtures, Jest factory functions) with copy-paste ready snippets.
Define a clear workflow: identify test data needs → choose fixture pattern (factory, builder, static) → implement → validate fixture output.
Include specific patterns like pytest's @pytest.fixture with scope options, conftest.py organization, or Jest's beforeEach setup with example input/output.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actionable content—the skill system handles activation; the body should teach how to generate fixtures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code examples, no commands, no specific fixture generation patterns, no framework-specific guidance. It only describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, and no validation checkpoints. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no separation of concerns. Despite mentioning multiple frameworks (jest, pytest), none are linked to specific resources. | 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
3076d78
- 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.