webflow-rate-limits
Handle Webflow Data API v2 rate limits \u2014 per-key limits, Retry-After\ \ headers,\nexponential backoff, request queuing, and bulk endpoint optimization.\n\ Use when hitting 429 errors, implementing retry logic,\nor optimizing API request\ \ throughput.\nTrigger with phrases like \"webflow rate limit\", \"webflow throttling\"\ ,\n\"webflow 429\", \"webflow retry\", \"webflow backoff\", \"webflow too many requests\"\ .\n"
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill webflow-rate-limits --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.
# Webflow Rate Limits ## Overview Handle Webflow Data API v2 rate limits using the SDK's built-in retry, manual backoff strategies, request queuing, and bulk endpoints to maximize throughput without hitting 429 errors. ## Prerequisites - `webflow-api` SDK installed - Understanding of async/await patterns - Knowledge of your site plan's rate limits ## Webflow Rate Limit Rules ### Per-Key Rate Limit
What does the webflow-rate-limits skill do?
Handle Webflow Data API v2 rate limits \u2014 per-key limits, Retry-After\ \ headers,\nexponential backoff, request queuing, and bulk endpoint optimization.\n\ Use when hitting 429 errors, implementing retry logic,\nor optimizing API request\ \ throughput.\nTrigger with phrases like \"webflow rate limit\", \"webflow throttling\"\ ,\n\"webflow 429\", \"webflow retry\", \"webflow backoff\", \"webflow too many requests\"\ .\n"
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill webflow-rate-limits --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.