Agent skill · data analytics · jeremylongshore
linear-performance-tuning
Improve Linear GraphQL latency and throughput by reducing field, connection, pagination, and polling cost. Use when queries are slow, complex, or exhausting shared budgets. Trigger with "optimize Linear GraphQL", "reduce Linear query complexity", or "speed up Linear sync".
Why this skill is useful
Provides specific caching strategies and optimization techniques for Linear API queries that the AI wouldn't reliably generate on its own.
What it needs
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 Query Performance Tuning Overview Tune the measured operation rather than applying guessed delays, and preserve correctness with bounded pagination and reconciliation. 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 Each property costs 0.1 complexity point, each object 1 point, and connections multiply child cost by the requested page size or default 50, rounded up. A single query cannot exceed 10,000 complexity points; hourly complexity and request limits are shared by user or app actor. Filtering server-side, requesting explicit page sizes, ordering by updated time, and using webhooks reduce unnecessary work. 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. Measure operation latency, requested fields, connection fan-out, page sizes, complexity header, payload bytes, and cache hit rate. 2. Replace broad SDK model walks with a purpose-built GraphQL query when only a narrow projection is needed. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-performance-tuning