mock-generator
Mock Generator - Auto-activating skill for Test Automation. Triggers on: mock generator, mock generator Part of the Test Automation skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.01xAverage 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/mock-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 duplicate trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific capabilities: describe what types of mocks are generated (e.g., 'Generates mock objects, test stubs, and fake data for unit testing frameworks like Jest, Pytest, or Mockito')
Expand trigger terms with natural variations: 'mock', 'stub', 'fake', 'test double', 'mock data', 'mock API', 'unit test setup'
Add explicit 'Use when...' clause: 'Use when the user needs to create mock objects for testing, generate fake data, or set up test doubles for dependencies'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Mock Generator' without explaining what concrete actions it performs. There are no specific capabilities listed like 'generates mock objects', 'creates test doubles', or 'stubs API responses'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and while it mentions triggers, they are just the skill name repeated. There is no 'Use when...' clause explaining scenarios for activation. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('mock generator, mock generator' is duplicated) and very limited. Missing natural variations users might say like 'create mocks', 'test doubles', 'stub', 'fake data', 'mock objects', or 'unit test mocks'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Mock Generator' is somewhat specific to testing contexts, which provides some distinctiveness. However, 'Test Automation' is broad and could overlap with other testing-related skills without clearer scope definition. | 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 template with no actionable content. It describes what a mock generator skill would do without providing any actual guidance, code examples, or concrete instructions for generating mocks. The content fails on all dimensions by being verbose yet empty of substance.
Suggestions
Add concrete, executable code examples showing how to create mocks using specific libraries (e.g., Jest's jest.fn(), Python's unittest.mock, or pytest-mock)
Include a quick-start section with copy-paste ready mock patterns for common scenarios (mocking API calls, database connections, external services)
Define a clear workflow for when and how to use different mock types (stubs, spies, fakes) with validation steps
Remove all generic boilerplate text and replace with specific, actionable guidance that Claude doesn't already know
| 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 mocks or use any mocking library. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for mock generation tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or related documentation. It mentions 'Related Skills' but provides no actual links or navigation. | 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
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.