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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill factory-pattern-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The repeated trigger term and boilerplate category mention add no value.
Suggestions
Add specific actions the skill performs, e.g., 'Generates factory classes for creating test data objects, builds fixture generators, creates builder patterns for test setup'
Add a 'Use when...' clause with natural trigger terms like 'test data', 'fixtures', 'mock objects', 'test object creation', 'factory for tests'
Specify the context/languages supported (e.g., 'for Python/JavaScript test suites') to distinguish from general factory pattern implementations
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the pattern ('Factory Pattern Creator') without describing any concrete actions. There's no explanation of what it actually does - no verbs describing capabilities like 'generates', 'creates', or 'configures'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Only mentions it's part of 'Test Automation' category. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'factory pattern creator' repeated twice, which is technical jargon. Missing natural user terms like 'test data', 'fixtures', 'mock objects', 'test setup', or 'generate test objects'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Factory Pattern' is somewhat specific to a design pattern domain, the lack of detail about what kind of factories (test data? object creation? which languages?) means it could overlap with general code generation or other testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance. It describes capabilities in abstract terms without providing any actual factory pattern implementation details, code examples, or concrete instructions. The content fails to teach Claude anything about factory patterns in test automation.
Suggestions
Add concrete, executable code examples showing factory pattern implementations (e.g., test data factories in Jest/pytest with actual code)
Define a clear workflow for when and how to create factory patterns, including steps like: identify test data needs, create base factory, add traits/variants, integrate with tests
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with specific factory pattern techniques, common patterns, and anti-patterns to avoid
Include at least one complete before/after example showing how factory patterns improve test code
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about factory patterns. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually create a factory pattern or provides any executable examples. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' as a capability but never actually provides any steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or supporting documentation. There's no structure that would help Claude navigate to more specific information. | 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.