mocking-test-generator
Generate unit tests with proper mocking for Python (unittest.mock/pytest) or Java (Mockito/JUnit) code. Use when users request test generation, unit tests with mocks, or testing code that has external dependencies like database calls, API requests, file I/O, or network operations. Automatically identifies dependencies to mock and creates executable, maintainable test code.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill mocking-test-generator87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is an excellent skill description that hits all the key criteria. It provides specific capabilities (unit test generation with mocking), names concrete frameworks and dependency types, includes an explicit 'Use when' clause with natural trigger terms, and carves out a distinct niche that won't conflict with general coding skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate unit tests', 'proper mocking', specifies frameworks (unittest.mock/pytest, Mockito/JUnit), and details dependency types (database calls, API requests, file I/O, network operations). | 3 / 3 |
Completeness | Clearly answers both what ('Generate unit tests with proper mocking...identifies dependencies to mock and creates executable, maintainable test code') and when ('Use when users request test generation, unit tests with mocks, or testing code that has external dependencies'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'mocks', 'test generation', 'external dependencies', 'database calls', 'API requests', 'file I/O', 'network operations', plus language-specific framework names. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on unit test generation with mocking for Python/Java. The combination of mocking focus, specific frameworks, and dependency types creates distinct triggers unlikely to conflict with general coding or other testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability through executable code examples and good progressive disclosure via external reference files. The main weaknesses are moderate verbosity (explaining concepts Claude likely knows) and missing validation steps in the workflow for verifying generated tests are correct and executable.
Suggestions
Add a validation step to the workflow: 'Run generated tests to verify they execute without errors before delivering'
Trim the 'Always mock' and 'Never mock' lists - Claude understands these patterns; keep only non-obvious items
Remove the 'Ask clarifying questions if' section - this is standard Claude behavior that doesn't need explicit instruction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., explaining what to mock vs not mock is somewhat obvious to Claude). The workflow steps could be more condensed, and some sections like 'Ask clarifying questions if' add bulk without critical value. | 2 / 3 |
Actionability | Provides fully executable code examples for both Python and Java with complete imports, proper structure, and copy-paste ready patterns. The examples follow Arrange-Act-Assert pattern with concrete mock setup and verification. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced, but lacks validation checkpoints. There's no guidance on verifying generated tests actually run or pass, no feedback loop for fixing failing tests, and no explicit validation step before delivering output. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to Python and Java pattern files. The main skill provides quick-start examples while pointing to detailed reference files for comprehensive patterns. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.