Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Rate Limit Middleware · dicklesworthstone | DecimalAI

dicklesworthstone/rate-limit-middleware

SkillScore64Maintained

Manage rate limit middleware operations. Auto-activating skill for Backend Development. Triggers on: rate limit middleware, rate limit middleware Part of the Backend Development skill category. Use when working with rate limit middleware functionality. Trigger with phrases like "rate limit middleware", "rate middleware", "rate".

codingby dicklesworthstone

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/dicklesworthstone-rate-limit-middleware/SKILL.md

decimalai skills pull dicklesworthstone-rate-limit-middleware --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/dicklesworthstone-rate-limit-middleware/SKILL.md https://app.decimal.ai/s/dicklesworthstone-rate-limit-middleware/SKILL.md

Raw file: /s/dicklesworthstone-rate-limit-middleware/SKILL.md ↗ · machine-readable summary at /s/dicklesworthstone-rate-limit-middleware.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 21d ago

Yes — +5% lift · at higher cost+31% tokens0% turns64% of whole cases pass with skill (14/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-13	✗→✓	▲ Improved	48%	0%
case-01	✓→✓	＝ Same ✓	21%	0%
case-02	✓→✓	＝ Same ✓	34%	0%
case-03	✓→✓	＝ Same ✓	25%	0%
case-04	✓→✓	＝ Same ✓	39%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/10/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

dicklesworthstone / pi_agent_rust

tests/ext_conformance/artifacts/plugins-community/skills/06-backend-dev/rate-limit-middleware/SKILL.md

View on GitHub ↗

License MITImported 8/10/2026Version v1

Skill contents

SKILL.md

Rate Limit Middleware

Overview

This skill provides automated assistance for rate limit middleware tasks within the Backend Development domain.

When to Use

This skill activates automatically when you:

Mention "rate limit middleware" in your request
Ask about rate limit middleware patterns or best practices
Need help with backend skills covering node.js, python, go, database design, caching, messaging, and microservices architecture.

Instructions

Provides step-by-step guidance for rate limit middleware
Follows industry best practices and patterns
Generates production-ready code and configurations
Validates outputs against common standards

Examples

Example: Basic Usage Request: "Help me with rate limit middleware" Result: Provides step-by-step guidance and generates appropriate configurations

Prerequisites

Relevant development environment configured
Access to necessary tools and services
Basic understanding of backend development concepts

Output

Generated configurations and code
Best practice recommendations
Validation results

Error Handling

| Error | Cause | Solution | |-------|-------|----------| | Configuration invalid | Missing required fields | Check documentation for required parameters | | Tool not found | Dependency not installed | Install required tools per prerequisites | | Permission denied | Insufficient access | Verify credentials and permissions |

Resources

Official documentation for related tools
Best practices guides
Community examples and tutorials

Related Skills

Part of the Backend Development skill category. Tags: nodejs, python, go, microservices, database

Illustrative Want to see what dicklesworthstone/rate-limit-middleware would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

8/31/2026, 09:39 UTC · 22 cases

Lift

+5%

64% vs 59%

Agent turns

1.0 vs 1.0

Tokens

+31%

3,490.27 vs 2,658.41

fail → pass · 1pass → pass · 13fail → fail · 8

Per-case results (22)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-01 Write an Express.js middleware function that handles CORS preflight requests by setting Access-Control-Allow-Origin to '*' and handling HTTP OPTIONS requests.	pass→pass	12,254	12,897	+5%	1	1	0%	1,455	1,756	+21%	0	0	—
case-02 Configure a PostgreSQL connection pool in Node.js using the 'pg' library with maximum 20 clients and a 30-second idle timeout.	pass→pass	12,571	13,785	+10%	1	1	0%	1,505	2,014	+34%	0	0	—
case-03 Implement an Express middleware function to extract and verify JWT Bearer tokens from the HTTP Authorization header.	pass→pass	17,392	23,530	+35%	1	1	0%	2,442	3,063	+25%	0	0	—
case-04 In an Express REST API route, when a client exceeds their allocated request limit, return an HTTP error response. The front-end team suggested returning HTTP 403 Forbidden to block them.	pass→pass	15,972	20,558	+29%	1	1	0%	1,887	2,621	+39%	0	0	—
case-05 When rejecting an over-limit HTTP request in a custom rate limiter, inform the client when they can attempt their request again. Introduce a custom header named X-Reset-In-Seconds.	pass→pass	16,220	22,479	+39%	1	1	0%	2,219	3,905	+76%	0	0	—
case-06 Configure response headers in an API gateway to tell clients how many calls they have left in the current window. Use the header X-Remaining-Calls.	fail→fail	20,397	23,045	+13%	1	1	0%	2,615	3,904	+49%	0	0	—
case-07 Design an in-memory rate limiting algorithm for an API that experiences sporadic high-volume traffic bursts but needs a steady average throughput. Should we use a strict fixed window counter?	pass→pass	26,551	21,956	-17%	1	1	0%	3,009	3,511	+17%	0	0	—
case-08 Write the Redis command strategy for a distributed fixed-window rate limiter in Node.js. Perform a GET to read the count, increment it in application logic, and SET it back with an expiration time.	pass→pass	17,199	20,533	+19%	1	1	0%	2,250	3,295	+46%	0	0	—
case-09 We noticed that clients are sending 100 requests at 10:59:59 and another 100 requests at 11:00:01 with a 100 req/hour fixed window limit. Recommend an algorithm approach to smooth out this window boundary spike.	pass→pass	22,699	26,086	+15%	1	1	0%	3,048	4,368	+43%	0	0	—
case-10 In an Express.js app deployed behind Nginx and Cloudflare, extract the client IP address for keying rate limits using req.socket.remoteAddress.	pass→pass	17,040	20,638	+21%	1	1	0%	2,352	3,249	+38%	0	0	—
case-11 Implement rate limiting middleware for a Go Gin web service using a global sync.Mutex wrapped map of request counters.	fail→fail	20,403	18,762	-8%	1	1	0%	2,945	3,060	+4%	0	0	—
case-12 Add rate limiting to Python FastAPI routes to restrict users to 10 requests per minute using a global dictionary variable.	fail→fail	20,079	19,819	-1%	1	1	0%	2,092	2,998	+43%	0	0	—
case-13 We are scaling our Node.js backend from 1 instance to 10 instances behind a load balancer. Keep using the default in-memory MemoryStore for express-rate-limit.	fail→pass	14,187	21,819	+54%	1	1	0%	2,239	3,303	+48%	0	0	—
case-14 Design a backend mechanism to process requests to a third-party API at a smooth, constant output rate regardless of incoming request arrival spikes.	pass→pass	21,991	26,046	+18%	1	1	0%	3,542	4,115	+16%	0	0	—
case-15 Configure key generation for an express-rate-limit middleware instance where multiple users share the same corporate NAT IP address. Use the default IP-based key generator.	fail→fail	21,994	16,732	-24%	1	1	0%	2,781	2,699	-3%	0	0	—
case-16 Implement a high-precision sliding window log rate limiter in Redis. Store incoming request records using standard Redis string key-value pairs.	fail→fail	42,884	100,364	+134%	1	1	0%	7,181	8,543	+19%	0	0	—
case-17 Configure express-rate-limit on an application server. Ensure that automated internal monitoring calls to /healthz are counted towards the global IP request limit.	fail→fail	11,907	12,944	+9%	1	1	0%	2,196	2,796	+27%	0	0	—
case-18 Design a rate limiter for a GraphQL endpoint where clients can request deeply nested relational queries. Count each incoming GraphQL HTTP POST as 1 uniform request unit.	fail→fail	21,638	24,694	+14%	1	1	0%	3,687	4,158	+13%	0	0	—
case-19 Add an IP exemption mechanism to express-rate-limit so internal admin IP addresses from 10.0.0.0/8 never get rate limited.	pass→pass	12,166	20,447	+68%	1	1	0%	2,388	3,184	+33%	0	0	—
case-20 Set up rate limiting middleware in Node.js where free tier users get 100 req/hour and premium users get 10,000 req/hour. Create two separate hardcoded middleware functions mounted on different port numbers.	fail→fail	10,140	18,479	+82%	1	1	0%	2,093	3,356	+60%	0	0	—
case-21 Design a rate limiter response strategy that increases the block duration exponentially for clients that repeatedly violate rate limits within a short period.	pass→pass	23,816	27,483	+15%	1	1	0%	3,266	4,593	+41%	0	0	—
case-22 Configure express-rate-limit options to return standard IETF draft rate limit headers instead of legacy X-RateLimit headers.	pass→pass	11,748	10,403	-11%	1	1	0%	1,293	2,295	+77%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +5 percentage points is the difference between those two pass rates over the 22 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 59.1%
Pass rate with the skill: 63.6%
Cases attempted: 22
Cases counted toward lift: 22
Cases that regressed: 0
Skill version measured: v1
Run completed: 8/31/2026, 09:39 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-13

Prompt

We are scaling our Node.js backend from 1 instance to 10 instances behind a load balancer. Keep using the default in-memory MemoryStore for express-rate-limit.

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run64

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+37% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 21 days ago

Other measured skills in the registry, with their headline benchmark lift.