This skill enables Claude to implement multi-tier database caching solutions. It is triggered when the user requests database caching, performance improvements, or reduced database load. The skill utilizes Redis, in-memory caching, and CDN layers to optimize database performance by reducing database load, improving query latency, and supporting horizontal scaling with cache-aside, write-through, and read-through patterns. Use this skill when the user mentions terms like "database caching", "improve database performance", "reduce database load", or uses the `/caching` command.
87
53%
Does it follow best practices?
Impact
93%
1.01xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/database/database-cache-layer/skills/database-cache-layer/SKILL.mdRedis cache-aside with cache key design and invalidation
Redis client used
0%
41%
Cache-aside pattern
100%
100%
Structured cache keys
100%
100%
Cache key collision avoidance
100%
100%
Cache invalidation on update
100%
100%
Cache invalidation on delete
100%
100%
TTL / expiry set
100%
100%
Database load reduction
100%
100%
Cache serialization
0%
100%
Redis connection config
0%
70%
Multi-tier in-memory and Redis caching hierarchy
In-memory cache present
100%
100%
lru-cache or named equivalent
100%
100%
Redis as L2 cache
100%
100%
L1 checked before L2
100%
100%
L2 checked before DB
100%
100%
L1 populated on L2 hit
100%
100%
Both caches populated on DB hit
100%
100%
Multi-tier clearly documented
100%
100%
TTL differentiation
100%
100%
Write-through caching strategy with monitoring
Write-through pattern
100%
100%
Write-through not cache-aside on write
100%
100%
Redis used for caching
0%
37%
Cache hit rate metric
100%
100%
Cache miss metric
100%
100%
Monitoring output
30%
40%
Structured cache keys
100%
100%
CDN configuration present
100%
100%
CDN targets static assets
100%
100%
TTL configured
100%
100%
Monitoring adjustability
100%
100%
Read-through caching pattern
Read-through abstraction
100%
26%
Cache-only interface
100%
83%
DB fetch on cache miss
100%
100%
Redis as cache store
100%
100%
Structured cache keys
100%
100%
Key collision avoidance
100%
100%
TTL configured
100%
100%
No DB call on cache hit
100%
100%
Cache layer is configurable
100%
87%
Read-through described in docs
66%
0%
Horizontal scaling with distributed Redis cache
Redis as shared store
100%
80%
Redis enables sharing across instances
100%
100%
No instance-local-only caching
100%
100%
Configurable Redis connection
100%
70%
Structured cache keys
100%
100%
Cache invalidation present
100%
100%
TTL configured
100%
100%
Cache-aside or write-through pattern
100%
100%
Horizontal scaling described
100%
100%
Cache serialization
71%
100%
Cache monitoring and strategy adjustment
Hit counter tracked
100%
100%
Miss counter tracked
100%
100%
Hit rate computed
100%
100%
Metrics output
100%
100%
TTL is configurable
100%
100%
Monitoring informs TTL guidance
100%
100%
Redis used for caching
100%
87%
Structured cache keys
100%
100%
Simulation or demo script
100%
100%
Cache-aside or read-through used
100%
100%
Redis connection configurable
100%
87%
CDN static asset caching with cache invalidation
CDN config present
100%
100%
Static assets targeted
100%
100%
Differentiated TTLs
100%
100%
Long TTL for versioned assets
100%
100%
Short TTL or no-cache for HTML
100%
100%
Cache-Control headers set
100%
100%
Invalidation mechanism present
100%
100%
Invalidation targets HTML paths
100%
87%
README explains strategy
100%
100%
Monitoring or cache hit guidance
0%
40%
Cache key namespace design for multi-service Redis sharing
Redis used for both services
100%
100%
Service-level namespace prefix
100%
100%
Entity type in key
100%
100%
No key collision for same ID
100%
100%
Demo shows distinct keys
100%
100%
Serialization on write
100%
100%
Deserialization on read
100%
100%
TTL configured
100%
100%
README explains key convention
100%
100%
Configurable Redis connection
50%
100%
Full three-tier caching: in-memory L1, Redis L2, CDN L3
In-memory L1 cache
70%
70%
Redis L2 cache
80%
100%
CDN config for static assets
100%
100%
L1 checked before L2
100%
100%
L2 checked before DB
100%
100%
Tier population on miss
100%
100%
Differentiated TTLs
100%
100%
Structured cache keys
100%
100%
Demo shows per-tier hits
100%
100%
README describes three tiers
100%
100%
9fad7ed
Table of Contents
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.