customerio-rate-limits
Implement Customer.io rate limiting and backoff. Use when handling high-volume API calls, implementing retry logic, or hitting 429 errors. "customer.io 429", "customer.io backoff", "customer.io too many requests". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-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.
# Customer.io Rate Limits ## Overview Understand Customer.io's API rate limits and implement proper throttling: token bucket limiters, exponential backoff with jitter, queue-based processing, and 429 response handling. ## Rate Limit Reference | API | Endpoint | Limit | Scope | |-----|----------|-------|-------| | Track API | `identify`, `track`, `trackAnonymous` | ~100 req/sec | Per workspace | |
What does the customerio-rate-limits skill do?
Implement Customer.io rate limiting and backoff. Use when handling high-volume API calls, implementing retry logic, or hitting 429 errors. "customer.io 429", "customer.io backoff", "customer.io too many requests". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill customerio-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.