Agent skill · software engineering · jeremylongshore
clickup-rate-limits
Analyze and control ClickUp request concurrency from plan-aware per-token limits, response headers, bounded queues, and reset-based retries. Use when preventing or recovering from ClickUp 429 responses. Trigger with "ClickUp rate limit", "ClickUp 429", or "size ClickUp concurrency".
Why this skill is useful
Adds executable scripts for handling ClickUp API rate limits with backoff and queuing that aren't in public docs.
What it needs
Requires clickup account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickUp Rate-Limit Control Overview Size traffic from the token's observed budget and workload rather than hard-coded optimistic concurrency. Preserve headroom for every caller sharing that token. Prerequisites Sanitized X-RateLimit-Limit, Remaining, and Unix Reset values plus 429 history The Workspace plan hosting the token and inventory of all callers sharing it Queue, freshness, retry, and priority requirements Tool Discipline Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode. Current Contract Limits apply per personal or OAuth token and vary by the hosting Workspace plan. Current published limits are 100 requests/minute for Free Forever, Unlimited, and Business; 1,000 for Business Plus; 10,000 for Enterprise. A 429 response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset; reset is a Unix timestamp. Plan values are ceilings, not target throughput; leave headroom for interactive and recovery traffic. Authentication Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret. Instructions 1. Inventory tokens, Workspaces, plans, callers, endpoints, request bursts, and retry loops. 2. Capture current headers from bounded calls and convert reset timestamps safely. 3. Allocate budgets by priority and reserve explicit headroom for user and recovery operations. 4. Implement a bounded queue/token bucket with jitter and a maximum elapsed retry time. 5. Pause at 429 until reset; do not fan out retries or switch tokens to bypass policy. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-rate-limits