factory-pattern-creator
Factory Pattern Creator - Auto-activating skill for Test Automation. Triggers on: factory pattern creator, factory pattern creator Part of the Test Automation skill category.
36
3%
Does it follow best practices?
Impact
96%
0.98xAverage 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/factory-pattern-creator/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 extremely thin and template-like, providing almost no actionable information about what the skill does or when it should be selected. It reads like auto-generated boilerplate with a duplicated trigger term and no concrete capabilities listed. It would be nearly impossible for Claude to reliably select this skill from a pool of similar test automation skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Generates factory classes and test data builders for creating test fixtures in automated test suites'.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating test factories, generating test data, building fixtures, or setting up object builders for testing.'
Expand trigger terms to include natural variations users would say: 'test factory', 'test data generation', 'fixture builder', 'factory method for tests', 'object mother pattern'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a pattern ('Factory Pattern Creator') and a domain ('Test Automation') but provides no concrete actions. There is no mention of what the skill actually does—no verbs describing specific capabilities like 'generates factory classes', 'creates test data builders', etc. | 1 / 3 |
Completeness | The 'what' is essentially absent—we only know it relates to factory patterns and test automation but not what it concretely does. The 'when' is missing entirely; there is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'factory pattern creator' repeated twice, which is not a natural phrase users would say. Missing common variations like 'test factory', 'test data', 'fixture', 'builder pattern', 'object mother', or 'test setup'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Factory Pattern Creator' is somewhat specific and unlikely to conflict with many other skills, but 'Test Automation' is broad enough to overlap with other testing-related skills. The lack of concrete scope makes it hard to distinguish from other test automation or design pattern skills. | 2 / 3 |
Total | 5 / 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 repeatedly references 'factory pattern creator' without ever defining what a factory pattern is in the testing context, providing code examples, or giving any actionable guidance. It fails on every dimension because it contains no technical content whatsoever.
Suggestions
Add concrete, executable code examples showing factory patterns in at least one test framework (e.g., a Python factory using pytest fixtures or a JavaScript factory for Jest), with input/output demonstrations.
Define a clear workflow: e.g., 1) Identify test data needs, 2) Create base factory, 3) Add trait/variant support, 4) Integrate into test suite—with validation steps at each stage.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actual technical instruction content.
Include specific factory pattern implementations (e.g., FactoryBot-style, builder pattern, fixture factories) with copy-paste ready code and link to an advanced reference file for complex scenarios like nested associations or sequences.
| 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 technical content. Every section restates the same vague idea ('factory pattern creator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no specific patterns, no executable instructions. The content only describes what it could do rather than actually doing or teaching anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no references to detailed materials, no links to examples or advanced guides, and no meaningful organization of content across sections. | 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.