One-click install
npx skills add https://github.com/fcalell/dotfiles --skill rate-limiting-fcalell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rate-limiting
Source: https://github.com/fcalell/dotfiles/tree/main/dot_claude/skills/rate-limiting
Command: npx skills add https://github.com/fcalell/dotfiles --skill rate-limiting-fcalell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rate-limiting patterns protect APIs from abuse, throttle heavy users, and prevent credential stuffing by enforcing quotas and cooldowns.

Core Features & Use Cases

  • Per-user and per-IP rate limiting with configurable limits
  • Endpoint-specific quotas and tiered plans (free/pro/enterprise)
  • Headers and retry guidance to support client backoff and observability
  • Use cases include public APIs, internal services, and partner integrations requiring controlled access.

Quick Start

Protect a new API by applying a rate-limit middleware to your routes with a default policy like 100 requests per minute and adjust per endpoint as needed.

Frequently Asked Questions about rate-limiting

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

FAQPage Schema
How do I enforce API rate limits to prevent abuse and credential stuffing?

API rate limiting prevents abuse by applying configurable middleware to enforce quotas and cooldowns across endpoints. You can set per-user and per-IP limits to throttle heavy usage and protect REST or GraphQL services.

Can I apply different rate limiting quotas for specific API endpoints and tiered plans?

Yes, rate limiting supports endpoint-specific quotas and tiered plans like free, pro, and enterprise. You can configure distinct limits for individual endpoints within both REST and GraphQL services to manage controlled access.

Does API rate limiting work with both REST and GraphQL services?

Yes, API rate limiting works with both REST and GraphQL services. The middleware enforces per-user, per-IP, or per-key quotas across your endpoints to prevent abuse and control access.

How do I ensure rate limits stay accurate across multiple requests with authenticated users?

Rate limiting integrates with durable storage or external services to maintain cross-request accuracy. The middleware recognizes authenticated user IDs when available to enforce precise per-user quotas.

Do I need standard rate-limit headers for clients to handle API backoff correctly?

Yes, standard rate-limit headers provide retry guidance to support client backoff and observability. Including these headers helps clients handle throttling gracefully when they hit endpoint quotas.