Agent skill · software engineering · jeremylongshore
linear-common-errors
Diagnose Linear GraphQL and SDK failures from transport, response, and request evidence. Use when an integration returns partial data, authentication failures, rate limits, invalid input, or missing resources. Trigger with "debug Linear GraphQL", "Linear API error", or "why did Linear SDK fail".
Why this skill is useful
Provides specific diagnostic scripts and error handling patterns for the Linear API that the AI wouldn't reliably generate on its own.
What it needs
Requires jq 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 Error Triage Overview Classify a failure before changing code or credentials, because Linear can return GraphQL errors with HTTP 200 and throttling errors with HTTP 400. 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 Always inspect the GraphQL errors array; a response can include partial data and errors together. Rate limiting is identified by extensions.code: RATELIMITED in an HTTP 400 GraphQL response, not by assuming HTTP 429. The SDK exposes parsed LinearError details including query, variables, status, data, raw error, and per-error path/type when available. 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. Capture the operation name, HTTP status, GraphQL error code/path, SDK version, and redacted rate headers. 2. Separate authentication, authorization, input, not-found, complexity, endpoint-budget, and service-health failures. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/linear-common-errors