Linear Rate Limiting
This skill should be used when designing bulk operations against Linear — complexity budgets, exponential backoff, request pacing, and avoiding 429s. Activates on "linear rate limit", "linear 429", "linear throttle", "complexity budget".
What this skill does
# Linear Rate Limiting
Reference: https://linear.app/developers/rate-limiting
## Two budgets
Linear bills against:
1. **Request rate** — per-IP, per-token (tier dependent: free ~1500/h, paid higher)
2. **Complexity points** — per-token (~5000/h typical)
The **complexity** budget is what bites large queries. Each query has a cost based on:
- Field count
- Connection sizes (`first: 100` costs more than `first: 10`)
- Nested resolves
## Headers
Every response includes:
- `X-RateLimit-Limit` — allowance per window
- `X-RateLimit-Remaining` — remaining
- `X-RateLimit-Reset` — epoch when budget resets
- `X-Complexity` — this query's cost
- `X-Complexity-Limit`, `X-Complexity-Remaining`, `X-Complexity-Reset`
The `lib/client.ts` GraphQL wrapper exposes these as a callback:
```ts
client.onRateLimit((info) => {
if (info.complexityRemaining < 1000) backoff(info.resetIn);
});
```
## Backoff strategy
When you receive a 429 (or `complexity_limit` GraphQL error):
- Read `X-RateLimit-Reset` / `X-Complexity-Reset`
- Sleep until that epoch + 1s jitter
- Retry once; second 429 → DLQ + alert (don't bury the user under retries)
```ts
async function withBackoff<T>(fn: () => Promise<T>, max = 3): Promise<T> {
for (let i = 0; i < max; i++) {
try { return await fn(); }
catch (e: any) {
if (e.status !== 429) throw e;
const reset = Number(e.headers["x-ratelimit-reset"]) * 1000 - Date.now();
await new Promise(r => setTimeout(r, Math.max(reset, 1000) + Math.random() * 500));
}
}
throw new Error("rate-limit retries exhausted");
}
```
## Pacing for bulk operations
For >50 mutations, pace explicitly:
- 10 in flight max (token bucket capacity)
- 1 per 100ms refill
- Pause if `complexity_remaining < 30%`
Implementation in `lib/rate-limit.ts` (token bucket).
## Webhook back-pressure
Don't poll Linear when you can webhook instead. The bridge agents:
- Subscribe to webhooks for real-time changes
- Only poll for **reconciliation** (every 6h) or after webhook DLQ replay
## Tips
- Prefer one big query with all fields you need over many small ones (fewer round-trips, often lower total complexity)
- Don't request `first: 250` if you only need 10
- Cache slow-moving data (team list, label list) for the duration of a process
- Avoid `every:` and `none:` filters on large connections — they're expensive
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.