api-rate-limiting-config
Configure api rate limiting config operations. Auto-activating skill for API Development. Triggers on: api rate limiting config, api rate limiting config Part of the API Development skill category. Use when working with APIs or building integrations. Trigger with phrases like "api rate limiting config", "api config", "api". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill api-rate-limiting-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.
# Api Rate Limiting Config ## Overview This skill provides automated assistance for api rate limiting config tasks within the API Development domain. ## When to Use This skill activates automatically when you: - Mention "api rate limiting config" in your request - Ask about api rate limiting config patterns or best practices - Need help with api development skills covering rest, graphql, openapi,
What does the api-rate-limiting-config skill do?
Configure api rate limiting config operations. Auto-activating skill for API Development. Triggers on: api rate limiting config, api rate limiting config Part of the API Development skill category. Use when working with APIs or building integrations. Trigger with phrases like "api rate limiting config", "api config", "api". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill api-rate-limiting-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.
