unit-test-caching
tessl i github:giuseppe-trisciuoglio/developer-kit --skill unit-test-cachingUnit tests for caching behavior using Spring Cache annotations (@Cacheable, @CachePut, @CacheEvict). Use when validating cache configuration and cache hit/miss scenarios.
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
50%This skill provides comprehensive coverage of Spring caching test scenarios with good structural organization, but has a fundamental technical flaw: the test examples won't actually test caching because plain service instantiation bypasses Spring's proxy mechanism that enables caching. The content is also verbose with sections that don't add value for Claude, and could benefit from splitting detailed examples into separate files.
Suggestions
Fix the test examples to use Spring's test context (@SpringBootTest or @ExtendWith(SpringExtension.class) with proper configuration) so caching proxies are actually created and the tests work correctly
Remove or significantly condense the 'When to Use This Skill', 'Best Practices', and 'Common Pitfalls' sections as they contain information Claude already knows
Add a validation step showing how to verify the test configuration is actually testing caching (e.g., inspecting the cache directly via CacheManager)
Move the Maven/Gradle setup and extended examples to separate reference files, keeping SKILL.md as a concise overview with one complete working example
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'When to Use This Skill' that largely restates the obvious, and the 'Best Practices' and 'Common Pitfalls' sections contain generic advice Claude already knows. However, the code examples themselves are reasonably efficient. | 2 / 3 |
Actionability | The code examples are mostly complete but have critical issues: the tests won't actually work because they create plain service instances without Spring proxies, so caching annotations won't be processed. The tests verify mock calls but the cache behavior won't actually occur without proper Spring context setup. | 2 / 3 |
Workflow Clarity | The skill presents patterns in a logical sequence (setup → @Cacheable → @CacheEvict → @CachePut → conditional → keys), but lacks validation steps for verifying cache configuration is correct. There's no guidance on debugging when tests fail or verifying the test setup is actually testing caching. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the document is quite long (300+ lines) with all content inline. The Maven/Gradle setup and extensive examples could be split into separate reference files, with SKILL.md providing a concise overview. | 2 / 3 |
Total | 8 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific technical context (Spring Cache annotations), concrete actions (unit testing caching behavior), and explicit trigger conditions. The description is concise yet comprehensive, using third-person voice and domain-specific terminology that developers would naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Unit tests for caching behavior' with explicit Spring Cache annotations (@Cacheable, @CachePut, @CacheEvict) and mentions 'validating cache configuration and cache hit/miss scenarios'. | 3 / 3 |
Completeness | Clearly answers both what ('Unit tests for caching behavior using Spring Cache annotations') and when ('Use when validating cache configuration and cache hit/miss scenarios') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'unit tests', 'caching', 'Spring Cache', specific annotation names (@Cacheable, @CachePut, @CacheEvict), 'cache configuration', 'cache hit/miss'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Spring Cache annotations and caching unit tests. The combination of Spring-specific annotations and cache testing scenarios makes it clearly distinguishable from general testing or caching 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.