Idempotent API operations with idempotency keys, Redis caching, DB constraints. Use for payment systems, webhook retries, safe retries, or encountering duplicate processing, race conditions, key expiry errors.
97
96%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Redis idempotency middleware
Redis package
0%
100%
Key prefix format
33%
100%
TTL is 86400
25%
100%
Caches status + body
100%
100%
Replays status + body
100%
100%
res.json interception
100%
100%
Missing key passthrough
100%
100%
Header name
100%
100%
Middleware applied to mutations
100%
100%
Database-backed idempotency with concurrency
Table schema columns
50%
100%
expires_at index
0%
100%
SHA-256 request hash
100%
100%
Atomic INSERT ON CONFLICT
75%
100%
rowCount check
90%
100%
Completes with response
100%
100%
Marks failed on error
62%
100%
Hash mismatch error
60%
100%
Processing state error
70%
100%
Returns cached on completed
100%
100%
Failed state error
50%
100%
Idempotency key cleanup strategy
Batched DELETE with LIMIT
100%
100%
Deletes by expires_at
100%
100%
Hourly schedule
0%
100%
Logs deleted row count
100%
100%
Error handling in job
100%
100%
Low-traffic timing guidance
100%
100%
Table size alerting
100%
100%
Cleanup job failure monitoring
100%
100%
Partitioning consideration
0%
100%
90d6bd7
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.