linear-rate-limits
Handle Linear API rate limiting, complexity budgets, and quotas. Use when dealing with 429 errors, implementing throttling, or optimizing request patterns to stay within limits. "linear API quota", "linear complexity", "linear request limits". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill linear-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.
# Linear Rate Limits ## Overview Linear uses the **leaky bucket algorithm** with two rate limiting dimensions. Understanding both is critical for reliable integrations: | Budget | Limit | Refill Rate | |--------|-------|-------------| | **Requests** | 5,000/hour per API key | ~83/min constant refill | | **Complexity** | 250,000 points/hour | ~4,167/min constant refill | | **Max single query** | 10
What does the linear-rate-limits skill do?
Handle Linear API rate limiting, complexity budgets, and quotas. Use when dealing with 429 errors, implementing throttling, or optimizing request patterns to stay within limits. "linear API quota", "linear complexity", "linear request limits". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill linear-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.