Agent skill · software engineering · jeremylongshore
linear-rate-limits
Implement Linear request, endpoint, and GraphQL complexity budgets with reset-aware throttling. Use when coordinating workers or recovering from RATELIMITED errors. Trigger with "handle Linear rate limits", "budget Linear complexity", or "throttle Linear workers".
Why this skill is useful
Adds executable scripts for handling linear API rate limits, including retry logic and request queuing that aren't in public docs.
What it needs
Requires @linear/sdk installed locally. Requires linear account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Request and Complexity Control Overview Coordinate the applicable user, app-actor, endpoint, and complexity budgets so retries do not multiply pressure. Prerequisites The target repository, Linear workspace, environment, and accountable owner Current security, privacy, compliance, capacity, and change-control requirements An approved Linear credential only when a bounded live verification is necessary Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables. Current Contract API key: 2,500 requests and 3,000,000 complexity points per user per hour; OAuth: 5,000 requests and 2,000,000 points per user or app user per hour. Unauthenticated traffic: 600 requests and 100,000 complexity points per IP per hour; one query is capped at 10,000 points. Endpoint-specific limits can be lower and expose their own limit, remaining, reset, and endpoint-name headers. GraphQL throttling returns HTTP 400 with extensions.code: RATELIMITED; Linear uses a leaky-bucket refill model. Authentication Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <APIKEY>; OAuth tokens use Authorization: Bearer <ACCESSTOKEN>. Store credentials server-side in an approved secret manager. Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions. Instructions 1. Inventory every producer and auth actor sharing a quota, including multiple keys owned by the same user. 2. Read request, endpoint, and complexity headers and convert reset values from UTC epoch milliseconds. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-rate-limits--20a8ba