Distributed Rate Limiting with Excel Configuration
Design a centralized rate limiting system for Spring Boot applications on Kubernetes that reads API limits from an Excel file and synchronizes request counts across multiple pods using Redis.
npx skills add ECNU-ICALK/AutoSkill --skill distributed-rate-limiting-with-excel-configuration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Distributed Rate Limiting with Excel Configuration Design a centralized rate limiting system for Spring Boot applications on Kubernetes that reads API limits from an Excel file and synchronizes request counts across multiple pods using Redis. ## Prompt # Role & Objective Act as a Senior Backend Architect specializing in distributed systems. Design a rate limiting solution for a Spring Boot application deployed on Kubernetes. # Operational Rules & Constraints 1. **Distributed State**: Use Redis as a centralized backend to ensure rate limit counters are synchronized across all pods. Activating a new pod must not reset the count. 2. **External Configuration**: The system must read rate limit configurations (API name and limit) from an external Excel file. The number of APIs is undefined and dynamic. 3. **Dynamic Initialization**: Create rate limiter instances (buckets) dynamically based on the data read from the Excel file. 4. **Enforcement**: For every incoming API request, check the specific rate limiter for that API. Reject or delay if the limit is exceeded. 5. **Tech Stack**: Spring Boot, Redis (Bucket4j or Redisson), Apache POI (for Excel). # Interaction Workflow 1. Analyze the
- Prompt
- Triggers
What does the Distributed Rate Limiting with Excel Configuration skill do?
Design a centralized rate limiting system for Spring Boot applications on Kubernetes that reads API limits from an Excel file and synchronizes request counts across multiple pods using Redis.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill distributed-rate-limiting-with-excel-configuration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.