Rate Limit Middleware - Auto-activating skill for Backend Development. Triggers on: rate limit middleware, rate limit middleware Part of the Backend Development skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/rate-limit-middleware/SKILL.mdHTTP standard compliance for rate limit responses
HTTP 429 status code
100%
100%
Retry-After header
30%
70%
X-RateLimit-Limit header
50%
37%
X-RateLimit-Remaining header
50%
37%
X-RateLimit-Reset header
50%
37%
Configurable limit
100%
100%
Configurable window
100%
100%
Middleware pattern
100%
100%
Per-IP rate limiting
100%
100%
Algorithm choice
0%
0%
Step-by-step documentation
100%
100%
Without context: $0.3982 · 1m 34s · 25 turns · 25 in / 5,651 out tokens
With context: $0.4997 · 2m 9s · 29 turns · 29 in / 6,344 out tokens
Production-ready distributed rate limiting
Redis backend
100%
100%
HTTP 429 status code
100%
100%
Retry-After header
100%
100%
Standard rate limit headers
100%
100%
Sliding window or token bucket
100%
100%
Per-user or per-key limiting
100%
100%
Configurable parameters
100%
100%
Reusable middleware
100%
100%
Redis connection config
100%
100%
Documentation
100%
100%
Without context: $0.5183 · 2m 20s · 24 turns · 25 in / 8,182 out tokens
With context: $0.5741 · 2m 19s · 30 turns · 317 in / 8,219 out tokens
Idiomatic Go rate limit middleware
HTTP 429 status code
100%
100%
Retry-After header
0%
100%
Standard rate limit headers
0%
0%
Concurrent-safe implementation
100%
100%
http.Handler interface
100%
100%
Configurable via struct
100%
100%
Token bucket or sliding window
0%
100%
Per-client key
100%
100%
Stale entry cleanup
0%
0%
Documentation
100%
100%
Without context: $0.2547 · 1m 36s · 14 turns · 15 in / 4,119 out tokens
With context: $0.5937 · 2m 41s · 31 turns · 29 in / 8,545 out tokens
994edc4
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.