mock-generator
Mock Generator - Auto-activating skill for Test Automation. Triggers on: mock generator, mock generator Part of the Test Automation skill category.
36
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 extremely weak—it reads like an auto-generated stub rather than a useful skill description. It provides no concrete actions, has duplicated and minimal trigger terms, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of similar testing-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates mock objects, stubs, and test doubles for unit and integration tests. Creates mock API responses and fake data fixtures.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create mocks, stubs, fakes, test doubles, mock data, or mock API responses for testing purposes.'
Remove the duplicated trigger term and expand with natural variations users would say, such as 'mock', 'stub', 'fake data', 'test double', 'mock service', 'mock API', 'unit test setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Mock Generator' and mentions 'Test Automation' but provides no concrete actions. It doesn't describe what the skill actually does—no mention of generating mock objects, stubbing APIs, creating test doubles, or any specific capabilities. | 1 / 3 |
Completeness | The 'what' is essentially absent—it never explains what the skill does beyond its name. The 'when' is limited to a redundant trigger phrase with no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'mock generator, mock generator' (duplicated). It misses natural user terms like 'mock', 'stub', 'fake', 'test double', 'mock data', 'mock API', 'unit test mocks', etc. The repetition suggests auto-generated content with no thought to user language. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'mock generator' is somewhat specific to a niche (generating mocks for testing), which provides some distinctiveness. However, the vague 'Test Automation' category label could overlap with other testing-related skills, and the lack of concrete scope makes boundaries unclear. | 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 a hollow template with no actual instructional content. It repeatedly references 'mock generator' without ever defining what mocking patterns to use, which libraries to employ, or how to generate mocks. It provides no code, no examples, no workflows—just meta-descriptions of what a skill would theoretically do.
Suggestions
Add concrete, executable code examples showing mock generation in at least one framework (e.g., Jest's jest.fn(), pytest's unittest.mock.patch) with realistic input/output scenarios.
Define a clear workflow: e.g., 1) Identify dependencies to mock, 2) Choose mock type (stub/spy/fake), 3) Implement mock with specific code, 4) Verify mock interactions.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') that describe the skill itself rather than teaching how to generate mocks—these waste tokens without adding value.
Add references to detailed guides for specific frameworks (e.g., 'For Jest mocking patterns see [JEST_MOCKS.md]', 'For pytest fixtures see [PYTEST_MOCKS.md]') to support progressive disclosure.
| 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 ('mock generator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no specific commands, no library recommendations, no mock patterns. The content describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no steps whatsoever. 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—each section just restates the same abstract concept. | 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.