321-frameworks-spring-boot-testing-unit-tests
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit tests in Java code. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/321-frameworks-spring-boot-testing-unit-tests/SKILL.mdQuality
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 clearly defines its scope, lists concrete capabilities with specific annotations and test types, provides explicit trigger guidance, and proactively distinguishes itself from related skills. The cross-references to adjacent skills (@131 for framework-agnostic Java and @322 for integration tests) are particularly effective at reducing conflict risk. The description is comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and annotations: pure unit tests with @ExtendWith(MockitoExtension.class), slice tests with @WebMvcTest and @MockitoBean, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. | 3 / 3 |
Completeness | Clearly answers both 'what' (write unit tests for Spring Boot applications with specific test types) and 'when' (opens with 'Use when you need to write unit tests for Spring Boot applications' and provides explicit trigger examples). Also distinguishes scope from related skills with cross-references. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'unit tests', 'Spring Boot', 'controllers', 'JSON serialization', 'parameterized tests', 'test profiles', plus specific annotations like @WebMvcTest, @MockitoBean. Also includes explicit trigger phrases like 'Review Java code for Spring Boot unit tests' and 'Apply best practices for Spring Boot unit tests'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — explicitly scopes to Spring Boot unit testing and differentiates itself from framework-agnostic Java testing (@131) and Spring Boot integration tests (@322), making conflict with similar skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a pointer to a reference file rather than a standalone actionable guide. While it has reasonable structure with constraints and a workflow, it lacks any concrete code examples, specific test patterns, or executable guidance in the body itself. The skill would benefit significantly from including at least one or two concrete before/after code examples inline to make it immediately useful without requiring the reference file.
Suggestions
Add at least 2-3 concrete, executable code examples inline (e.g., a pure unit test with @ExtendWith(MockitoExtension.class), a @WebMvcTest slice test, and a @JsonTest example) so the skill is actionable without reading the reference.
Integrate the compilation/verification commands directly into the workflow steps rather than splitting them between Constraints and Workflow sections (e.g., Step 1 should include the actual compile command).
Remove or condense the 'What is covered' bullet list—it largely restates the skill description and doesn't add actionable value. Replace it with a quick-start example that demonstrates the most common pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' section is somewhat verbose and partially redundant with the description. The bullet list explaining what the skill covers reads more like a table of contents than actionable content. However, it's not egregiously padded—most content serves a purpose. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific test patterns shown. All substantive guidance is deferred to the reference file. The skill body describes rather than instructs—Claude would need to read the reference to know what to actually do. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with compilation checks and verification steps mentioned in constraints. However, the validation checkpoints are split between the Constraints section and the Workflow section, and the workflow steps themselves are vague ('Apply framework-aligned changes' gives no specifics). The compile-first and verify-after pattern is good but could be more tightly integrated. | 2 / 3 |
Progressive Disclosure | The skill references a single detailed reference file with a clear path, which is good one-level-deep disclosure. However, the bundle files were not provided, so we can't verify the reference exists. More importantly, the SKILL.md itself is too thin—it defers almost everything to the reference, making the body feel like a stub rather than a useful overview with actionable quick-start content. | 2 / 3 |
Total | 7 / 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.
- Repository
- jabrena/cursor-rules-java
- Commit
762cb86
- 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.