Agent skill · data analytics · jeremylongshore
linear-cost-tuning
Analyze and reduce the infrastructure and quota cost of a Linear integration through workload accounting, query budgets, and push-based updates. Use when a sync is wasteful, throttled, or expensive to operate. Trigger with "reduce Linear API load", "budget Linear queries", or "tune Linear integration cost".
Why this skill is useful
Provides specific optimization patterns and code examples for efficient Linear API usage that the AI wouldn't generate on its own.
What it needs
Requires linear account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Linear Workload and Capacity Tuning Overview Treat cost as the integration's compute, queue, storage, support, and quota consumption; do not claim a fixed Linear API price from cached documentation. 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 Linear publishes request and complexity budgets, not a universal per-request price; plan and contract entitlements are dynamic. Polling is discouraged; webhooks are the primary change signal when supported. Filtering, explicit page sizes, narrow field selection, and updated-time ordering reduce both query complexity and local processing. 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 requests, complexity, payload bytes, queue time, retries, storage growth, and operator toil by workflow. 2. Separate required freshness from habitual polling and replace supported polling loops with verified webhooks. 3. Set per-workload request and complexity budgets below the applicable shared limits. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-cost-tuning