Caching, locks and queues on Redis: TTL discipline, the lock that expires mid-work, and why a cache stampede shows up only under load.
SkillScore100Maintained
Automatic
◆Coding pack
Last verified 8/3/2026
What it changes
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
Without skill95%
With skill100%
Checks it passed that the model alone missed
Recommends using monotonic fencing tokens to invalidate late writes if a lock expires mid-task
Recommends background heartbeat renewal or watchdog processes to extend lock TTL while active work is ongoing
1 fixed21 passed either way0 still failing0 broke
Pass-rate lift
+5 pp
Tokens
+8%
Agent turns
0%
Response time
+6%
Model gemini-3.6-flashMeasured 8/3/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
I am designing a Redis-backed task queue and caching layer for a high-throughput API and want to ensure proper expiration handling so keys do not accumulate indefinitely. Please generate a detailed best-practices specification covering key lifecycle management, TTL configuration patterns, and queue cleanup strategies.
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends background heartbeat renewal or watchdog processes to extend lock TTL while active work is ongoing
Missed
Passed
Recommends using monotonic fencing tokens to invalidate late writes if a lock expires mid-task
Missed
Passed
case-01 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md4 linessingle file
redis-patterns
Caching, locks and queues on Redis: TTL discipline, the lock that expires mid-
work, and why a cache stampede shows up only under load.