mock-generator
Mock Generator - Auto-activating skill for Test Automation. Triggers on: mock generator, mock generator Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill mock-generatorOverall
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 providing meaningful trigger guidance. It lacks any concrete actions, has duplicate trigger terms, and provides no context for when Claude should select this skill over others. The description would be nearly useless for skill selection in a library of 10+ skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates mock objects, stub functions, and fake data for unit and integration tests'
Expand trigger terms with natural variations users would say: 'mock', 'stub', 'fake', 'test double', 'mock data', 'mock API', 'test fixtures'
Add an explicit 'Use when...' clause describing scenarios: 'Use when the user needs to create test mocks, generate fake data for testing, or set up stub implementations for dependencies'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Mock Generator' without describing any concrete actions. It doesn't explain what the skill 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 the 'when' guidance is just a repeated trigger term without explaining use cases or scenarios when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('mock generator, mock generator' is duplicated) and limited. Missing natural variations users might say like 'create mocks', 'stub', 'fake data', 'test doubles', or 'mock objects'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Mock Generator' and 'Test Automation' provide some domain specificity, the lack of concrete details about what kind of mocks (API mocks, unit test mocks, data mocks) could cause overlap with other testing-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive guidance. It describes what a mock generator skill would do in abstract terms but provides zero actionable content—no code examples, no specific mocking libraries (Jest, pytest-mock, etc.), no patterns, and no workflows. The content fails on all dimensions by being verbose yet empty of useful information.
Suggestions
Add executable code examples showing how to create mocks in specific frameworks (e.g., Jest mock functions, pytest-mock fixtures, or unittest.mock)
Include concrete patterns like mocking HTTP requests, database calls, or external services with copy-paste ready code
Define a clear workflow: identify dependency → choose mock strategy → implement mock → verify mock was called correctly
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually generate mocks or use any mocking library. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content only lists vague capabilities without any sequence of actions, validation steps, or concrete process for mock generation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources, examples, or reference materials. No useful navigation or organization exists. | 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.