Individual skill
rate-limiting-architect
Designs distributed token bucket, leaky bucket, and tiered rate limiting architectures to prevent abuse.
skills/architecture/rate-limiting-architect/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 593 bytesSKILL.mdcore · 1,735 bytesexamples/example.mddoc · 1,048 bytes
Read excerpt
## Purpose
Architect scalable, distributed rate limiting and traffic throttling systems using Token Bucket, Leaky Bucket, Sliding Window Log, or Sliding Window Counter algorithms to protect APIs from abuse and noisy neighbors.
## When to Use
- Protecting public APIs from DDoS, credential stuffing, and scraping.
- Implementing multi-tier usage limits (Free vs Pro vs Enterprise quotas).
- Managing outbound rate limits to comply with third-party vendor quotas (OpenAI, Stripe).
## What to Analyze
1. **Algorithm Selection**: Token Bucket (bursts allowed) vs Leaky Bucket (smooth pacing) vs Sliding Window Counter (memory efficient).
2. **Identification Key**: User ID, Organization ID, API Token, or IP address (with X-Forwarded-For trust validation).