hootsuite-rate-limits
Implement Hootsuite rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Hootsuite. Trigger with phrases like "hootsuite rate limit", "hootsuite throttling", "hootsuite 429", "hootsuite retry", "hootsuite backoff". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hootsuite-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.
# Hootsuite Rate Limits ## Overview Handle Hootsuite API rate limits. The API returns `429 Too Many Requests` with `Retry-After` headers when limits are exceeded. ## Rate Limits | Endpoint | Limit | Window | |----------|-------|--------| | General API | Varies by plan | Per minute | | Message scheduling | ~100/hour | Per hour | | Media upload | ~50/hour | Per hour | | Token refresh | ~10/hour | Pe
What does the hootsuite-rate-limits skill do?
Implement Hootsuite rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Hootsuite. Trigger with phrases like "hootsuite rate limit", "hootsuite throttling", "hootsuite 429", "hootsuite retry", "hootsuite backoff". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill hootsuite-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.