unit-test-controller-layer
tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-controller-layerUnit tests for REST controllers using MockMvc and @WebMvcTest. Test request/response mapping, validation, and exception handling. Use when testing web layer endpoints in isolation.
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 code examples covering the full range of MockMvc testing scenarios. The main weaknesses are verbosity in introductory sections and the monolithic structure that could benefit from progressive disclosure to separate files. The missing @BeforeEach annotation on setUp() is a notable oversight that could cause confusion.
Suggestions
Remove or significantly trim the 'When to Use This Skill' section - these use cases are self-evident from the skill title
Add @BeforeEach annotation to the setUp() method to make the example fully correct and executable
Consider splitting advanced topics (headers, content negotiation, troubleshooting) into a separate ADVANCED.md file
Remove Maven/Gradle setup section - Claude knows how to add Spring Boot test dependencies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity like the 'When to Use This Skill' section listing obvious use cases, and the Maven/Gradle setup which Claude likely knows. The best practices and common pitfalls sections add value but could be more concise. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all Java test code is complete, copy-paste ready with proper imports, annotations, and assertions. Covers GET, POST, PUT, DELETE with concrete MockMvc patterns. | 3 / 3 |
Workflow Clarity | While individual test patterns are clear, there's no explicit workflow for setting up a test class from scratch. The setUp() method is shown but not annotated with @BeforeEach, and there's no validation checkpoint for ensuring tests actually run correctly. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic document (~300 lines) that could benefit from splitting advanced topics (content negotiation, headers) into separate files. References at the end are external links rather than internal skill files. | 2 / 3 |
Total | 9 / 12 Passed |
Activation
85%This is a well-crafted skill description that clearly defines its scope (Spring web layer unit testing) with specific technologies and testing concerns. It includes an explicit 'Use when' clause that helps Claude understand when to select this skill. The main weakness is trigger term coverage could be broader to capture more natural user phrasings.
Suggestions
Add common user variations like 'controller tests', 'API tests', 'Spring MVC testing', or 'HTTP endpoint tests' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Unit tests for REST controllers using MockMvc and @WebMvcTest', 'Test request/response mapping, validation, and exception handling'. Names specific technologies and testing concerns. | 3 / 3 |
Completeness | Clearly answers both what ('Unit tests for REST controllers using MockMvc and @WebMvcTest. Test request/response mapping, validation, and exception handling') and when ('Use when testing web layer endpoints in isolation') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'MockMvc', '@WebMvcTest', 'REST controllers', 'web layer endpoints', but missing common user variations like 'controller tests', 'API tests', 'Spring MVC tests', or 'HTTP endpoint testing'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focusing specifically on web layer/controller testing with MockMvc and @WebMvcTest. The 'in isolation' qualifier and specific Spring testing annotations distinguish it from integration tests or other testing skills. | 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.