Api Rate Limiting Config - Auto-activating skill for API Development. Triggers on: api rate limiting config, api rate limiting config Part of the API Development skill category.
34
Quality
3%
Does it follow best practices?
Impact
86%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/api-rate-limiting-config/SKILL.mdREST API rate limiting with standard headers and status codes
HTTP 429 status
100%
100%
X-RateLimit-Limit header
100%
100%
X-RateLimit-Remaining header
100%
100%
X-RateLimit-Reset header
100%
100%
Retry-After header
100%
100%
Production-ready config
100%
100%
Standard algorithm
100%
100%
Error response body
100%
100%
Step-by-step docs
100%
100%
Per-identifier limiting
100%
100%
Error handling
50%
100%
Without context: $0.4036 · 2m 14s · 16 turns · 15 in / 8,505 out tokens
With context: $0.6674 · 2m 52s · 30 turns · 78 in / 10,791 out tokens
GraphQL API rate limiting by query complexity
Complexity-based limiting
100%
100%
HTTP 429 status
25%
0%
GraphQL error format
100%
100%
X-RateLimit headers
0%
0%
Retry-After header
100%
0%
Per-client limiting
100%
100%
Production config
75%
50%
Depth or field limits
66%
50%
Step-by-step explanation
100%
100%
Error handling
50%
60%
Without context: $0.6596 · 3m 34s · 23 turns · 23 in / 13,444 out tokens
With context: $0.6944 · 3m 32s · 26 turns · 26 in / 12,813 out tokens
OpenAPI rate limit documentation and standards validation
HTTP 429 response documented
100%
100%
X-RateLimit headers in spec
100%
100%
Retry-After header in spec
100%
100%
Headers on 2xx responses
100%
100%
Reusable header components
100%
100%
Validation step performed
100%
91%
Valid YAML/JSON output
100%
87%
Rate limit policy description
100%
100%
Step-by-step guide
100%
100%
Standards reference
50%
100%
Without context: $0.5078 · 2m 56s · 30 turns · 32 in / 8,020 out tokens
With context: $0.7938 · 3m 36s · 35 turns · 1,838 in / 10,331 out tokens
0c08951
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.