skills.rest
Prathmesh2000
Prathmesh2000COMMUNITY
Explore all skills by this author →
GitHub

rate-limiting

Implement Redis-backed rate limiting with per-key scoping and custom 429 responses.

1|Updated Mar 4, 2026
Search Tags:#api#redis#middleware#rate-limiting#express#throttling
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill rate-limiting-prathmesh2000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rate-limiting
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/rate-limiting
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill rate-limiting-prathmesh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rate limiting and abuse prevention for APIs and services, preventing overload by controlling traffic and protecting credentials.

Core Features & Use Cases

  • Per-IP, per-user, and per-endpoint limits with configurable windows and burst handling.
  • Redis-backed state storage for scalable, shared rate tracking across instances.
  • Flexible responses with custom 429 handlers and guidance for clients on retry.

Quick Start

Configure and apply per-IP, per-user, and per-endpoint limits in your API to prevent abuse.

Frequently Asked Questions about rate-limiting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement rate limiting in an Express API to prevent abuse?▼

Rate limiting in an Express API is implemented by enforcing usage limits through configurable middleware, preventing abuse by controlling traffic across per-IP, per-user, and per-endpoint scopes. This protects services from overload.

Does Redis-backed rate limiting work for sliding window scenarios?▼

Redis-backed rate limiting supports sliding window implementations to track state accurately across distributed instances. This enables scalable, shared traffic control and custom burst handling for high-volume APIs.

Can I configure custom 429 responses for clients hitting API rate limits?▼

Custom 429 responses can be configured to provide guidance for clients when they hit API rate limits. This flexible response handling ensures clients receive proper retry instructions during throttling events.

What is the best way to scope API throttling rules for different endpoints?▼

Scoping API throttling rules is best handled by applying per-endpoint limits with configurable windows and custom burst handling. This granular approach ensures specific endpoints receive tailored traffic control.

Do I need Redis to handle rate limiting across multiple API instances?▼

Redis is required for shared rate tracking state when distributing rate limiting across multiple API instances. It provides scalable state management to accurately enforce limits and handle bursts in distributed environments.

Related Skills

Explore More Software Engineering Skills→
AradotsoAradotso
5

terraform-data-engineering-iac

Provision AWS S3 buckets and EC2 instances with Terraform for data engineering.

Official
Advanced
exilonXexilonX

marketplace-rate-limiting

Implement rate-limit resilience for VTEX marketplace API calls with exponential backoff and Retry-After handling.

Community
Intermediate
nextplus896nextplus896

laravel-routing

Configure Laravel routes with model binding and route-level authorization.

Community
Advanced
jezwebjezweb
961

vercel-kv

Implements Redis-compatible key-value storage for Next.js apps with caching, sessions, and rate limiting.

Community
Intermediate