unit-test-service-layer
tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-service-layerUnit tests for service layer with Mockito. Test business logic in isolation by mocking dependencies. Use when validating service behaviors and business logic without database or external services.
Validation
75%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | 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 | 12 / 16 Passed | |
Implementation
65%This is a solid, actionable skill with excellent executable code examples covering the breadth of Mockito testing patterns. Its main weaknesses are verbosity (explaining when to use the skill, including full dependency blocks) and lack of a clear step-by-step workflow for writing tests. The content would benefit from trimming obvious explanations and potentially splitting advanced patterns into separate files.
Suggestions
Remove the 'When to Use This Skill' section - Claude understands when to use unit tests with mocks
Add a brief workflow summary at the top: 'Identify dependencies → Mock with @Mock → Inject with @InjectMocks → Arrange-Act-Assert → Verify interactions'
Consider moving Maven/Gradle setup to a separate SETUP.md file or condensing to a single line reference
Split advanced patterns (async testing, spies, argument capturing) into an ADVANCED.md file to reduce main file length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the 'When to Use This Skill' section which explains obvious use cases Claude would understand. The Maven/Gradle setup is standard boilerplate that could be trimmed. However, the code examples themselves are reasonably efficient. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all snippets are copy-paste ready with proper imports, annotations, and complete test methods. Covers single dependency, multiple dependencies, exception handling, argument capturing, and verification patterns with concrete, runnable code. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for writing a service test from scratch. The content presents patterns but lacks a clear sequence like 'identify dependencies → create mocks → arrange → act → assert → verify'. The troubleshooting section helps but doesn't provide validation checkpoints during test creation. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear section headers, but it's a long monolithic file (~300 lines) that could benefit from splitting advanced topics (async testing, spies, argument capturing) into separate reference files. The external references at the end are appropriate but inline content is heavy. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
90%This is a well-crafted skill description that clearly communicates its purpose and when to use it. It excels at trigger term coverage and completeness with an explicit 'Use when' clause. The main weakness is that the capabilities could be more specific by listing concrete Mockito operations rather than general testing concepts.
Suggestions
Add specific Mockito actions like 'verify method invocations', 'stub return values', 'capture arguments with ArgumentCaptor' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (service layer testing with Mockito) and describes the general action (test business logic by mocking dependencies), but doesn't list multiple specific concrete actions like 'verify method calls', 'stub return values', or 'capture arguments'. | 2 / 3 |
Completeness | Clearly answers both what ('Unit tests for service layer with Mockito. Test business logic in isolation by mocking dependencies') and when ('Use when validating service behaviors and business logic without database or external services') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'unit tests', 'service layer', 'Mockito', 'business logic', 'mocking dependencies', 'database', 'external services'. Good coverage of terms developers naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting service layer testing specifically with Mockito, distinct from general unit testing, integration testing, or repository testing skills. The combination of 'service layer', 'Mockito', and 'mocking dependencies' creates a well-defined scope. | 3 / 3 |
Total | 11 / 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.