generating-test-doubles
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-test-doublesThis skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill content is primarily descriptive rather than instructive, explaining concepts Claude already understands (test doubles, mocks, stubs) without providing any executable code or concrete commands. The examples describe what the skill 'will do' abstractly rather than showing actual generated output or plugin invocation syntax. The content reads like marketing copy rather than actionable technical guidance.
Suggestions
Replace abstract examples with actual executable code showing generated test doubles (e.g., a complete Jest mock example with the actual generated code output)
Add concrete plugin invocation syntax showing exactly how to call the test-doubles-generator plugin with required parameters
Remove the 'Overview', 'How It Works', and 'When to Use' sections entirely - Claude knows what test doubles are and when to use them
Add validation steps for verifying generated test doubles compile and integrate correctly with the test suite
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with unnecessary explanations Claude already knows (what mocks/stubs/spies are, when to use them). The 'Overview', 'How It Works', and 'When to Use' sections explain basic testing concepts rather than providing actionable instructions. | 1 / 3 |
Actionability | No executable code, no concrete commands, no actual test double examples. The 'Examples' section describes what the skill will do abstractly rather than showing actual generated code or how to invoke the plugin. | 1 / 3 |
Workflow Clarity | The 'How It Works' section provides a basic 3-step sequence, but lacks any validation checkpoints, error handling, or concrete commands. No feedback loops for when generation fails or produces incorrect output. | 2 / 3 |
Progressive Disclosure | Content is organized into sections, but everything is in one file with no references to external documentation. The content that exists is mostly filler that could be removed rather than split into separate files. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms that developers would use, explicitly states both what the skill does and when to use it, and has a clear niche that distinguishes it from other skills. The inclusion of explicit slash commands further strengthens its distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'create mocks, stubs, spies, and fakes', 'analyzes dependencies', 'generates appropriate test doubles based on the chosen testing framework'. Also names specific frameworks (Jest, Sinon). | 3 / 3 |
Completeness | Clearly answers both what ('automatically create mocks, stubs, spies, and fakes', 'analyzes dependencies') AND when ('Use this skill when you need to generate test doubles... to isolate units of code during testing') with explicit trigger guidance including commands. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'test doubles', 'mocks', 'stubs', 'spies', 'fakes', 'unit testing', plus explicit commands '/gen-doubles' and '/gd'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test double generation with distinct triggers. The specific terminology (mocks, stubs, spies, fakes) and dedicated commands ('/gen-doubles', '/gd') make it unlikely to conflict with general testing or code generation skills. | 3 / 3 |
Total | 12 / 12 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.