rate-limiter-config
Configure rate limiter config operations. Auto-activating skill for Security Fundamentals. Triggers on: rate limiter config, rate limiter config Part of the Security Fundamentals skill category. Use when configuring systems or services. Trigger with phrases like "rate limiter config", "rate config", "rate". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill rate-limiter-config --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.
# Rate Limiter Config ## Overview This skill provides automated assistance for rate limiter config tasks within the Security Fundamentals domain. ## When to Use This skill activates automatically when you: - Mention "rate limiter config" in your request - Ask about rate limiter config patterns or best practices - Need help with essential security skills covering authentication, input validation, s
What does the rate-limiter-config skill do?
Configure rate limiter config operations. Auto-activating skill for Security Fundamentals. Triggers on: rate limiter config, rate limiter config Part of the Security Fundamentals skill category. Use when configuring systems or services. Trigger with phrases like "rate limiter config", "rate config", "rate". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill rate-limiter-config --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 jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 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.